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 197518 - AssertionError at org.netbeans.modules.cnd.debugger.gdb2.GdbDebuggerImpl.interpUpdate
Summary: AssertionError at org.netbeans.modules.cnd.debugger.gdb2.GdbDebuggerImpl.inte...
Status: RESOLVED INCOMPLETE
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Egor Ushakov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 00:35 UTC by tbrunhoff
Modified: 2011-10-03 16:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 178220

Attachments
stacktrace (2.15 KB, text/plain)
2011-04-07 00:36 UTC, tbrunhoff 		Details
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 tbrunhoff 2011-04-07 00:35:58 UTC 
Build: NetBeans IDE Dev (Build 201103260400)
VM: Java HotSpot(TM) Client VM, 19.0-b09, Java(TM) SE Runtime Environment, 1.6.0_23-b05
OS: Linux

User Comments:
tbrunhoff: entering a watch that looks like m_stbl->stsz

tbrunhoff: entering a watch value that looks like this->m_stbl->stps->getHeadroom()




Stacktrace: 
java.lang.AssertionError
   at org.netbeans.modules.cnd.debugger.gdb2.GdbDebuggerImpl.interpUpdate(GdbDebuggerImpl.java:2303)
   at org.netbeans.modules.cnd.debugger.gdb2.GdbDebuggerImpl.access$2200(GdbDebuggerImpl.java:137)
   at org.netbeans.modules.cnd.debugger.gdb2.GdbDebuggerImpl$19.onDone(GdbDebuggerImpl.java:2458)
   at org.netbeans.modules.cnd.debugger.gdb2.mi.MICommandManager.dispatch(MICommandManager.java:149)
   at org.netbeans.modules.cnd.debugger.gdb2.mi.MIProxy.dispatch(MIProxy.java:175)
   at org.netbeans.modules.cnd.debugger.gdb2.Gdb$MyMIProxy.dispatch(Gdb.java:1063)
Comment 1 tbrunhoff 2011-04-07 00:36:01 UTC 
Created attachment 107573 [details]
stacktrace
Comment 2 Egor Ushakov 2011-09-26 15:34:00 UTC 
would you please attach gdb log?
Comment 3 tbrunhoff 2011-09-26 15:41:34 UTC 
> would you please attach gdb log?

From April?? It does not exist.

You should file a new bug that any exception that occurs when gdb is running will automatically attach the gdb log.
Comment 4 Egor Ushakov 2011-09-26 15:51:08 UTC 
Not necessary to attach the exact log from April))
Couldn't you reproduce it with the current bits?
Comment 5 Egor Ushakov 2011-10-03 14:51:48 UTC 
Todd, it is impossible to fix it without the log, please attach and reopen when reproduced. BTW, have you changed gdb version? Old gdb may be the reason of such issues.
Comment 6 tbrunhoff 2011-10-03 16:44:52 UTC 
GNU gdb (GDB) Fedora (7.2-51.fc14)

I'll watch for a recurrence.