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 125932 - NetBeans aborts debugging session if gdb issues a warning
Summary: NetBeans aborts debugging session if gdb issues a warning
Status: CLOSED WONTFIX
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: _ gordonp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-24 15:45 UTC by simonis
Modified: 2009-06-25 10:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
gdb_command_line.txt (2.94 KB, text/plain)
2008-01-24 15:46 UTC, simonis
Details
gdb-cmds8219.log_1 (3.37 KB, text/plain)
2008-01-24 15:47 UTC, simonis
Details
gdb-cmds8219.log (4.70 KB, text/plain)
2008-01-24 15:47 UTC, simonis
Details
gdb_helper_8220.log (16 bytes, text/plain)
2008-01-24 15:49 UTC, simonis
Details
gdb_helper_8221.sh (318 bytes, text/plain)
2008-01-24 15:49 UTC, simonis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description simonis 2008-01-24 15:45:40 UTC
The gdb-engine of NetBeans aborts a debugging session if the underlying debugger issues a warning. This should be
handled more gracefully (i.e. present the warning to the user and ask him if he wants to proceed or not).

I'll attach some files which demonstrate the behaviour:

gdb_command_line.txt
--------------------
This is what gdb displays on the comamnd line if I debug the same program. You can see the warning, but there's no core
and I can "step" to the next instruction.

gdb_helper* and gdb-cmds8219.log_1
-----------------------------------
The log-files at the time when the debugger stopped at the breakpoint and the following dialog appeared:
"The GDB Debugger has reported a corrupted stack. The debug session must be terminates" <OK>

gdb-cmds8219.log
-----------------
The log file after I pressed the <OK> button.

I could solve the problem by using a newer version of gdb (6.6 instead 6.3) but that doesn't change the fact that the NB
gdb engine shouldn't abort execution because of a warning.

Regards,
Volker

PS: 
my NB version:
--------------
Product Version: NetBeans IDE 6.0 (Build 200711261600)
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05
System: Linux version 2.6.5-7.283-bigsmp running on i386; UTF-8; en_US (nb)

C/C++ plugin
------------
Version: 1.2.1 
Source: NetBeans
Comment 1 simonis 2008-01-24 15:46:38 UTC
Created attachment 55512 [details]
gdb_command_line.txt
Comment 2 simonis 2008-01-24 15:47:23 UTC
Created attachment 55513 [details]
gdb-cmds8219.log_1
Comment 3 simonis 2008-01-24 15:47:54 UTC
Created attachment 55514 [details]
gdb-cmds8219.log
Comment 4 simonis 2008-01-24 15:49:17 UTC
Created attachment 55515 [details]
gdb_helper_8220.log
Comment 5 simonis 2008-01-24 15:49:45 UTC
Created attachment 55516 [details]
gdb_helper_8221.sh
Comment 6 _ gordonp 2008-02-04 17:54:10 UTC
I don't have a gdb 6.3 on my Ubuntu Linux system and can't easily
build it. The sources depend on termcap and ubuntu doesn't have a termcap in its package
repository. Since my goal of building it was to verify that gdb aborted when this situation
occurred, and since it no longer happens with gdb 6.6 (our reference version on Linux), I'm
closing as WONTFIX.