Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 132427 - NPE in 'Disassembly' tab
NPE in 'Disassembly' tab
Product: cnd
Classification: Unclassified
Component: -- Other --
All All
: P1 (vote)
: 6.x
Assigned To: Egor Ushakov
Depends on:
  Show dependency treegraph
Reported: 2008-04-09 16:00 UTC by soldatov
Modified: 2008-04-17 10:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT

gdb-log (12.22 KB, text/plain)
2008-04-09 20:04 UTC, alexandrov

Note You need to log in before you can comment on or make changes to this bug.
Description soldatov 2008-04-09 16:00:27 UTC
- Create Args project
- Select project in 'Projects' tab and call context menu. Select 'Step into' menu item
==> Debugger started
- Push 'Window|Debugging|Dissambly' menu item
- Move cursor on some register
==> On other machines tooltip appears. On my machine I see NPE (always) instead of tooltip.

	at org.openide.util.RequestProcessor$
[catch] at org.openide.util.RequestProcessor$
Comment 1 soldatov 2008-04-09 16:03:55 UTC
And other scenario:
- Create Args project
- Select project in 'Projects' tab and call context menu. Select 'Step into' menu item
==> Debugger started
- Push 'Window|Debugging|Registers' menu item
==> NPE

	at java.lang.String.compareTo(
	at org.netbeans.modules.cnd.debugger.gdb.ui.RegistersTopComponent$
	at org.netbeans.modules.cnd.debugger.gdb.ui.RegistersTopComponent$
	at java.util.Arrays.mergeSort(
	at java.util.Arrays.mergeSort(
	at java.util.Arrays.mergeSort(
	at java.util.Arrays.mergeSort(
	at java.util.Arrays.mergeSort(
	at java.util.Arrays.sort(
	at java.util.Collections.sort(
	at org.netbeans.modules.cnd.debugger.gdb.ui.RegistersTopComponent.<init>(
	at org.netbeans.modules.cnd.debugger.gdb.ui.RegistersTopComponent.getDefault(
	at org.netbeans.modules.cnd.debugger.gdb.ui.RegistersTopComponent.findInstance(
	at org.netbeans.modules.cnd.debugger.gdb.ui.RegistersAction.actionPerformed(
	at javax.swing.AbstractButton.fireActionPerformed(
	at javax.swing.AbstractButton$Handler.actionPerformed(
	at javax.swing.DefaultButtonModel.fireActionPerformed(
	at javax.swing.DefaultButtonModel.setPressed(
	at javax.swing.AbstractButton.doClick(
	at javax.swing.plaf.basic.BasicMenuItemUI.doClick(
	at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(
	at java.awt.Component.processMouseEvent(
	at javax.swing.JComponent.processMouseEvent(
	at java.awt.Component.processEvent(
	at java.awt.Container.processEvent(
	at java.awt.Component.dispatchEventImpl(
	at java.awt.Container.dispatchEventImpl(
	at java.awt.Component.dispatchEvent(
	at java.awt.LightweightDispatcher.retargetMouseEvent(
	at java.awt.LightweightDispatcher.processMouseEvent(
	at java.awt.LightweightDispatcher.dispatchEvent(
	at java.awt.Container.dispatchEventImpl(
	at java.awt.Window.dispatchEventImpl(
	at java.awt.Component.dispatchEvent(
[catch] at java.awt.EventQueue.dispatchEvent(
	at org.netbeans.core.TimableEventQueue.dispatchEvent(
	at java.awt.EventDispatchThread.pumpOneEventForFilters(
	at java.awt.EventDispatchThread.pumpEventsForFilter(
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(
	at java.awt.EventDispatchThread.pumpEvents(
	at java.awt.EventDispatchThread.pumpEvents(
Comment 2 Jesse Grodnik 2008-04-09 16:33:06 UTC
Can you please fully characterize the machine on which this defect occurs: OS version, Java version etc. Also can you
characterize one or two machines on which defect does NOT occur.
Comment 3 soldatov 2008-04-09 17:01:12 UTC
Assembler fails on such machine:
SLES 9, 64-bit, java 1.6.0 (1.6.0_04 I think), gdb 6.6

Works correctly on Ubuntu 7 (32 but) and Fedora Core (32 bit)

Comment 4 Egor Ushakov 2008-04-09 17:41:01 UTC
Could you please attach gdb log
Comment 5 Egor Ushakov 2008-04-09 17:51:43 UTC
first part fixed in:
Comment 6 alexandrov 2008-04-09 20:04:36 UTC
Created attachment 59927 [details]
Comment 7 Egor Ushakov 2008-04-09 20:29:16 UTC
The problem is that gdb gives 50 register names and 58 register values.
I will fix exception, but we still have to find out why gdb reports inconsistent information on this platform,
and what are those 8 extra registers we have values but not names for.
Comment 8 _ gordonp 2008-04-09 21:07:22 UTC
Could the extra values be because 8 registers are 64-bit and the rest 32-bit?
Comment 9 Egor Ushakov 2008-04-10 10:15:47 UTC
The problem is:
gdb is asked for register names too early (before the debugged program is loaded)
and gives 32-bit registers. After 64-bit program is loaded it uses 64-bit registers.
Comment 10 Egor Ushakov 2008-04-10 10:43:12 UTC
Fixed in the changeset:
Comment 11 Jesse Grodnik 2008-04-10 21:34:22 UTC
Fixed in trunk. Escalated to P1. Request permission to fix in RC2.
Comment 12 soldatov 2008-04-11 11:09:05 UTC
verified in RC1 build + jar with fixes from developer
Comment 14 soldatov 2008-04-17 10:09:44 UTC
verified in NetBeans 6.1 RC2

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo