Bug 59446

Summary: crash on loading project
Product: [Applications] kdevelop Reporter: Simon Huerlimann <simon.huerlimann>
Component: CPP DebuggerAssignee: KDevelop Developers <kdevelop-devel>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: 3.0.0a4   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:

Description Simon Huerlimann 2003-06-06 21:14:39 UTC 
Version:           3.0.0a4 CVS (using KDE KDE 3.1.2)
Installed from:    Debian testing/unstable Packages

If i open a project, gideon begins to open files. Then it crashes. As far as I can see, all files get opened, the crash is then the next visible action.

I don't know how to get a backtrace, if someone can give me a hint, I will post the backtrace.

gideon gives some output on the shell:

kdecore (KAccel): WARNING: KKeySequence::init( seq ): key[0] is null.
kdecore (KAccel): WARNING: KKeySequence::init( seq ): key[0] is null.
QMetaObject::findSignal:GDBDebugger::GDBController: Conflict with GDBDebugger::DbgController::rawGDBBreakpointList(char*)
QMetaObject::findSignal:GDBDebugger::GDBController: Conflict with GDBDebugger::DbgController::rawGDBBreakpointSet(char*,int)
QMetaObject::findSignal:GDBDebugger::GDBController: Conflict with GDBDebugger::DbgController::rawGDBDisassemble(char*)
QMetaObject::findSignal:GDBDebugger::GDBController: Conflict with GDBDebugger::DbgController::ttyStdout(const char*)
QMetaObject::findSignal:GDBDebugger::GDBController: Conflict with GDBDebugger::DbgController::ttyStderr(const char*)
QObject::connect: No such slot GDBDebugger::DisassembleWidget::slotBPState(const Breakpoint&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
Alarm clock

May this helps. I'll have a look at the suspected files, but my c++ knowlegde is very limited...
Comment 1 Amilcar do Carmo Lucas 2003-06-06 21:31:52 UTC 
This seams to be debugger related.

to get a backtrace, open a konsole and type:
gdb gideon
run

Then it should crash, go back to the konsole and type:
backtrace

That's it!
Comment 2 Simon Huerlimann 2003-06-06 22:35:02 UTC 
thanx for the gdb stuff! 
 
the bug itself is resolved too :-) i was installing handmade deb's and missed to install the 
gideon-plugin pkg:-( 
 
still lerning a lot...