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 227431 - gdb variables get confused
Summary: gdb variables get confused
Status: RESOLVED INVALID
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 7.3
Hardware: PC Linux
: P2 normal (vote)
Assignee: henk89
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-13 17:15 UTC by tbrunhoff
Modified: 2013-03-27 16:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tbrunhoff 2013-03-13 17:15:35 UTC

    
Comment 1 tbrunhoff 2013-03-13 17:19:46 UTC
This may turn out to be a gdb bug.

- I start a gdb session with breakpoints.
- I hit a break point and there are no problems.
- I add some watch variables, and eventually, when I step I get messages from gdb (via a pop up) that looks like:

Type <data variable, no debug info> is not a structure or union type.

In the debugger console this corresponds to the following:

(gdb) 
653-var-evaluate-expression var72
652^error,msg="Type <data variable, no debug info> is not a structure or union type."

This remains even if I remove all the watch variables.
Comment 2 tbrunhoff 2013-03-18 14:30:30 UTC
Sorry... for got to include:

Product Version: NetBeans IDE Dev (Build 201301110001)
Updates: Updates available
Java: 1.7.0_10; Java HotSpot(TM) Client VM 23.6-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_10-b18
System: Linux version 3.6.11-1.fc16.x86_64 running on i386; UTF-8; en_US (nb)
User directory: /home/toddb/.netbeans/dev
Cache directory: /home/toddb/.cache/netbeans/dev
Comment 3 henk89 2013-03-27 14:32:13 UTC
What version of gdb do you use?

This is really a gdb bug. I'll file it and provide a link here.
Comment 4 tbrunhoff 2013-03-27 14:56:40 UTC
Thanks. I have seen this off and on for years. Do you think any of the newer versions of gdb have this fixed? And although this is a gdb bug, is it possible that NB does something specific (perhaps stimulated by structures in my code) that tickles the gdb bug?

GNU gdb (GDB) Fedora (7.3.50.20110722-16.fc16)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Comment 5 henk89 2013-03-27 16:00:36 UTC
I don't think so.

http://sourceware.org/bugzilla/show_bug.cgi?id=15313