How to get Netbeans to catch a SIGABRT?
-
Back in the day, when I used Visual Studio on Windows, you could break on any exceptions or abrupt termination. With Netbeans and Linux C++ development, however, it seems like I have 3 options: Pass and continue (terminates the program), discard and stop, discard and continue. None of these do anything remotely useful. Discard and continue is probably the most useful one, in that it lets you keep on going until you hit a segmentation fault. My goal is to figure out which line of code is causing the initial SIGABRT. Any suggestions?
-
Back in the day, when I used Visual Studio on Windows, you could break on any exceptions or abrupt termination. With Netbeans and Linux C++ development, however, it seems like I have 3 options: Pass and continue (terminates the program), discard and stop, discard and continue. None of these do anything remotely useful. Discard and continue is probably the most useful one, in that it lets you keep on going until you hit a segmentation fault. My goal is to figure out which line of code is causing the initial SIGABRT. Any suggestions?
No idea about Netbeans (frankly, this is the first time I've heard anybody is using that for C++ development), but you can set gdb to stop on a signal here are the instructions[^].
-
No idea about Netbeans (frankly, this is the first time I've heard anybody is using that for C++ development), but you can set gdb to stop on a signal here are the instructions[^].
-
No idea about Netbeans (frankly, this is the first time I've heard anybody is using that for C++ development), but you can set gdb to stop on a signal here are the instructions[^].
Nemanja Trifunovic wrote:
frankly, this is the first time I've heard anybody is using that for C++ development
Second time (I used just a bit). :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]