Tue Apr 02, 2013 11:53 pm
Every time I debug the game that I'm working on using kdevelop as the debugger I get a crash in kdevelop. More precisely, it aborts. There is no call stack.
This 'only' happens if I have breakpoints set, but I kinda need to have breakpoints set.
It may depend on the specific breakpoints -- after a half-dozen crashes I'm stopping for a bit.
Given that I'm not getting a call stack it's hard to make a useful bug report. Any thoughts on what to do?
Wed Apr 10, 2013 3:25 pm
You can run kdevelop through gdb:
Then when it crashes, type "thread apply all bt" to get a backtrace similar to what drkonqui gives you.
I'm working on python language support for KDevelop.
Registered users: alake, Andreas Mair, Azzart, baaann, Baidu [Spider], Bing [Bot], bravegag, chimichurri, colomar, einar, Exabot [Bot], ggael, Google [Bot], google01103, Hans, ivan, jensreuterberg, jospoortvliet, kopykat, La Ninje, lazyit, Majestic-12 [Bot], mbohlender, Murz, notmart, sjarmouni, TheraHedwig, trebor, wolfi323, Yahoo [Bot]