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.

Bug 257995 - IDE debugger misleads user if SIGSEGV occurs while it is set to "nostop" in console or .gdbinit
Summary: IDE debugger misleads user if SIGSEGV occurs while it is set to "nostop" in c...
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Maria Tishkova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-15 18:25 UTC by Vladimir Kvashin
Modified: 2016-09-01 19:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2016-02-15 18:25:15 UTC 
I had a segmentation fault in my program.
When debugging it, I've got a dialog box with 3 choices: 
Discard and Pause / Discard and Continue / Forward and Continue

I selected "Discard and Pause" to see the stack, etc - but the program coredumped and debugger exited.

The problem was that long, long ago I wrote in my .gdbrc:
handle SIGSEGV nostop pass

Well, it's my fault... but it would be fine if IDE recognized this and didn't offer wrong choices.

It could say something like
"SIGSEGV processing was set to "nostop pass" either in your .gdbinit file or manually in debugger console"
And the only choice is "OK"

Implementation-wise comment:
it's easy to know how the gdb processes the SIGSEGV (or other  signal) via the command:
#handle SIGSEGV