kdevelop aborted on start of debug session

Bug #87616 reported by Ian Hollander
2
Affects Status Importance Assigned to Milestone
kdevelop (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Kdevelop3 crashed after clicking the "start debug arrow" button. I'm guessing that it may have something to do with what happened during previous debug session. I had attempted to add a watch for the "->first" object contained in a particular STL map. The debugger first complained that it couldn't access the location(?) and then abruptly stop running.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb4ebec17 in GDBDebugger::VarItem::handleSpecialTypes ()
   from /usr/lib/kde3/libkdevdebugger.so
#7 0xb4ebf4c3 in GDBDebugger::VarItem::updateValue ()
   from /usr/lib/kde3/libkdevdebugger.so
#8 0xb4ec1df4 in GDBDebugger::VariableTree::handleVarUpdate ()
   from /usr/lib/kde3/libkdevdebugger.so
#9 0xb4ead64f in GDBDebugger::GDBCommand::invokeHandler ()
   from /usr/lib/kde3/libkdevdebugger.so
#10 0xb4ea8f75 in GDBDebugger::GDBController::processMICommandResponse ()
   from /usr/lib/kde3/libkdevdebugger.so
#11 0xb4ea9473 in GDBDebugger::GDBController::slotDbgStdout ()
   from /usr/lib/kde3/libkdevdebugger.so
#12 0xb4ea5b13 in GDBDebugger::GDBController::qt_invoke ()
   from /usr/lib/kde3/libkdevdebugger.so
#13 0xb71f0813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb77efbd3 in KProcess::receivedStdout () from /usr/lib/libkdecore.so.4
#15 0xb77efe98 in KProcess::childOutput () from /usr/lib/libkdecore.so.4
#16 0xb77efec9 in KProcess::slotChildOutput () from /usr/lib/libkdecore.so.4
#17 0xb77eff2a in KProcess::qt_invoke () from /usr/lib/libkdecore.so.4
#18 0xb71f0813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb71f112a in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb757d6b3 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#21 0xb72133d2 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#22 0xb71879e8 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#23 0xb7189817 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#24 0xb78c4d52 in KApplication::notify () from /usr/lib/libkdecore.so.4
#25 0xb711a1e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#26 0xb7179de1 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#27 0xb712ed07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb71a20be in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb71a1ece in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0xb7189591 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x0804e404 in ?? ()
#32 0xbf8b2438 in ?? ()
#33 0x0809d8c0 in ?? ()
#34 0xbf8b2418 in ?? ()
#35 0x00000001 in ?? ()
#36 0x080528d5 in ?? ()
#37 0x00000001 in ?? ()
#38 0x080529c0 in ?? ()
#39 0x08052979 in ?? ()
#40 0x0805213c in ?? ()
#41 0x08052128 in _IO_stdin_used ()
#42 0x2b43e9ec in ?? ()
#43 0x00000000 in ?? ()

ProblemType: Bug
Date: Sat Feb 24 12:37:22 2007
DistroRelease: Ubuntu 7.04
Uname: Linux litebright 2.6.20-8-386 #2 Tue Feb 13 05:15:43 UTC 2007 i686 GNU/Linux

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in kdevelop:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdevelop:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.