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.
If a project's Run Directory is set to nonexistent location then 1) I will see a dialog Warning GDB has unexpectedly stopped with return 127 2) After clicking OK, the Progress dialog "Starting debugger/Starting gdb" will stay until I click Cancel. The messages are not intuitive, there are many reasons why a debugger can fail. Even if it can be a GDB bug, I would expect that NetBeans will check if the directory exists and Show a correct error message. Please work on fixing. Thank you.
Fixed in: http://hg.netbeans.org/cnd-main/rev/9ddba01f4658
Integrated into 'main-silver', will be available in build *201408120001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/9ddba01f4658 User: Nikolay Koldunov <henk89@netbeans.org> Log: Fixed #238582 - GDB has unexpectedly stopped with return 127
Verified in trunk build 20140812.
Integrated into 'releases/release801', will be available in build *201409171118* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/043a810e355e User: Nikolay Koldunov <henk89@netbeans.org> Log: Fixed #238582 - GDB has unexpectedly stopped with return 127 (transplanted from 9ddba01f46587281c6d2b3f79753c1c2789b6809)
This problem still persists in 8.0.1. 8.0 was just fine but I updated and now I cannot debug any C project anymore.
I am experiencing the same issue with Mac OSX Yosemite. I have checked it with version 8.0, 8.01, 8.02. My gdb is working properly in terminal. I think the issue is related to Yosemite. Any suggestions?
it's the same for el capitan sadly
I only recently started using NetBeans 8.0.2 for a C++ project, and I'm also getting this error, trying to debug into a test. I'm on Mac El Capitan 10.11.6
I upgraded to 8.2, and am still getting this (El Capitan 10.11.6, latest XCode 8.2.1)
Which gdb you are using in El Capitan?
Hmm... I didn't realize that gdb was not installed by default on Mac anymore. I followed the instructions to install it using brew and codesign it. The version is 7.12.1 I also updated the reference to its proper location in /usr/local/bin/gdb rather than the default of /usr/bin/gdb. https://sourceware.org/gdb/wiki/BuildingOnDarwin It only still seems to be partially working. When I select a CppUnit test and go Debug Test, if I have a breakpoint on the first line in the main of the testrunner file, it will break on that line. But when I put breakpoints on a line in the test file, or in my source code, it doesn't break on either of those lines, it just completes the test. 1 comment: since there was not even a gdb binary at my initial configuration, it is very extremely misleading for a geeky/techy message like "GDB has unexpectedly stopped"--it never even existed, let alone being started! The IDE properly displayed the launch command in red, to indicate the file didn't even exist!
Ok, after searching all over the web, I finally discovered someone said I needed to add -g to my g++ compilation options. That worked! (At least on Linux)
Please re-open if it doesn't work with latest dev version http://bits.netbeans.org/dev/nightly/latest/