Debugger crash on detach
ghost at cs.msu.su
Wed Dec 20 12:35:51 UTC 2006
On Wednesday 20 December 2006 15:16, David Nolden wrote:
> Currently kdevelop crashes every time I stop debugging, no matter what way I
> use, with this backtrace:
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1241811280 (LWP 23635)]
> [New Thread -1262650464 (LWP 23652)]
> [KCrash handler]
> #6 0xffffe410 in __kernel_vsyscall ()
> #7 0xb6010770 in raise () from /lib/tls/i686/cmov/libc.so.6
> #8 0xb6011ef3 in abort () from /lib/tls/i686/cmov/libc.so.6
> #9 0xb6009dbb in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
> #10 0xb4e53d08 in GDBDebugger::GDBController::slotDbgStdout (this=0x8bd2358,
> buf=0xbf904787 "&\"detach\\n\"\n~\"Detaching from
This is "fixed" now. The assert was complaining that we've got output to
unknown command, because for detaching we directly write "detach" to a pipe,
bypassing everything. Since fixing "detach" is hard for KDevelop3, I've removed
the assert and added comment.
> Also deleting Breakpoints still sometimes doesn't work and gives me
> warning-popups etc.
That's new bug. Care to post the output in gdb window with
"Show internal commands" enabled?
More information about the KDevelop-devel