This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I often experience many issues involving how Netbeans handle C++ projects. First of all, it sometimes (randomly) chooses not to activate the "Step into" global option and I can't just press F7 to start debugging, I have to right-click the project (which is set as main project!) and click "Step into". Secondly, very often clicking "Step into" makes Netbeans point me at the end of my few short functions (actually, at the end of the first one) and nothing works, neither "Step into" nor "Step over". Restarting the debugger doesn't help, I have to restart Netbeans and re-add all my watches... It really hampers writing performance, so I consider it critical. I use Ubuntu 11.04 x64.
please attach gdblog (http://wiki.netbeans.org/GdbLog) from one of these sessions
I found this at the end of the log (just when it hangs): ~"/build/buildd/gdb-7.2/gdb/thread.c:598: internal-error: is_thread_state: Assertion `tp' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? " ~"(y or n) [answered Y; input not from terminal]\n" ~"/build/buildd/gdb-7.2/gdb/thread.c:598: internal-error: is_thread_state: Assertion `tp' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nCreate a core file of GDB? " ~"(y or n) [answered Y; input not from terminal]\n" So I suppose I should report it to GDB?
I think so, anyway it is strange that the next gdb session is impossible until you restart the IDE...
Yes, it is strange. It took me some time to make this error appear again (Murphy's laws in effect) to report it here but once it happened, stopping execution, rebuilding everything and clicking "Step into" hung IDE immediately...
Sorry for double posting, but I remembered one thing - when these things crash I also get a compiz crash. I have to restart it then using "compiz --replace"...
OK, but even though GDB seems to be at its fault we still have two Netbeans issues: 1) to make GDB work again I have to restart Netbeans (and Netbeans should close GDB process at termination so this shouldn't happen) 2) I often have to manually click "Step into" by right-clicking the main project, even though it should be accessible via main Debug menu and the F7 key.
agree, will fix
No QA action needed.
we need to detect that gdb has died (or core dumped), show notification to the user and close the session. Now if gdb dies all buttons are still enabled but do nothing and it is impossible to kill the session.
Fixed in: http://hg.netbeans.org/cnd-main/rev/51a4b9da00a2
Integrated into 'main-golden', will be available in build *201205290002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/51a4b9da00a2 User: Nikolay Koldunov <henk89@netbeans.org> Log: Fixed #198498 - C++ debugger randomly chooses not to run at all (until Netbeans restart)
Extra fix: http://hg.netbeans.org/cnd-main/rev/8b85ec33feae
Integrated into 'main-golden', will be available in build *201206090001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/8b85ec33feae User: Nikolay Koldunov <henk89@netbeans.org> Log: Extra fix #198498 - C++ debugger randomly chooses not to run at all (until Netbeans restart)