[Bug 59447] New: crash on loading project

simon.huerlimann at access.unizh.ch simon.huerlimann at access.unizh.ch
Fri Jun 6 22:38:05 UTC 2003


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=59447     
           Summary: crash on loading project
           Product: kdevelop
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: simon.huerlimann at access.unizh.ch


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...




More information about the KDevelop-devel mailing list