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 18243 - Exception occurs when clicking on Breakpoint line in the Debugger Window
Summary: Exception occurs when clicking on Breakpoint line in the Debugger Window
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: Marian Petras
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-30 21:31 UTC by John Baker
Modified: 2001-12-04 03:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exceptions stack-trace (2.98 KB, text/plain)
2001-12-03 13:21 UTC, Jan Chalupa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Baker 2001-11-30 21:31:24 UTC
To reproduce:

1) Try debugging the Clock example
2) Mount ffjuser30/sampledir
3) Build clock
4) Set a breakpoint in ClockFrame.java in the main method
5) Start the Debugger
6) In the Debugger window, double-click on the Breakpoint item,
   "Line ClockFrame.java:151"

Result:
Fri Nov 30 13:03:39 PST 2001: java.lang.IllegalStateException: Posted StackTrace
Annotation: Exception occurred in Request Processor
Nested annotation: The data object ClockFrame.java is invalid; you may not call
getNodeDelegate on it; if this is
thrown please create an issue in openide/loaders assigned to jglick@netbeans.org
org.openide.util.RequestProcessor$Holder: Posted StackTrace(task
org.netbeans.core.ModuleActions$1@2b0028 [-96, 1,
-1])
        at
org.openide.util.RequestProcessor$Task.createHolder(RequestProcessor.java:322)
        at org.openide.util.RequestProcessor.post(RequestProcessor.java:100)
        at org.openide.util.RequestProcessor.post(RequestProcessor.java:73)
        at org.netbeans.core.ModuleActions.invokeAction(ModuleActions.java:123)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.openide.explorer.view.TreeView.invokeAction(TreeView.java:886)
        at
org.openide.explorer.view.TreeView$ClickAdapter.mouseClicked(TreeView.java:974)
        at
java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:211)
        at java.awt.Component.processMouseEvent(Component.java:3718)
        at java.awt.Component.processEvent(Component.java:3544)
        at java.awt.Container.processEvent(Container.java:1164)
        at java.awt.Component.dispatchEventImpl(Component.java:2593)
        at java.awt.Container.dispatchEventImpl(Container.java:1213)
        at java.awt.Component.dispatchEvent(Component.java:2497)
        at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451)
        at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2230)
        at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125)
        at java.awt.Container.dispatchEventImpl(Container.java:1200)
        at java.awt.Window.dispatchEventImpl(Window.java:914)
        at java.awt.Component.dispatchEvent(Component.java:2497)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
        at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
        at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
 
Fri Nov 30 13:03:39 PST 2001: java.lang.IllegalStateException: The data object
ClockFrame.java is invalid; you may
not call getNodeDelegate on it; if this is thrown please create an issue in
openide/loaders assigned to
jglick@netbeans.org
java.lang.IllegalStateException: The data object ClockFrame.java is invalid; you
may not call getNodeDelegate on
it; if this is thrown please create an issue in openide/loaders assigned to
jglick@netbeans.org
        at org.openide.loaders.DataObject.getNodeDelegate(DataObject.java:239)
        at org.openide.text.EditorSupport$Editor.<init>(EditorSupport.java:515)
        at org.openide.text.EditorSupport$Editor.<init>(EditorSupport.java:505)
        at
org.netbeans.modules.java.JavaEditor$JavaEditorComponent.<init>(JavaEditor.java:947)
        at
org.netbeans.modules.java.JavaEditor.createJavaEditorComponent(JavaEditor.java:862)
        at
org.netbeans.modules.java.JavaEditor.createCloneableTopComponent(JavaEditor.java:854)
        at
org.openide.text.EditorSupport$Del.createCloneableTopComponent(EditorSupport.java:704)
        at
org.openide.windows.CloneableOpenSupport.openCloneableTopComponent(CloneableOpenSupport.java:157)
        at
org.openide.text.CloneableEditorSupport.openAt(CloneableEditorSupport.java:1230)
        at
org.openide.text.EditorSupportLineSet$SupportLine.show(EditorSupportLineSet.java:81)
        at org.openide.text.Line.show(Line.java:119)
        at
org.netbeans.modules.debugger.support.nodes.BreakpointNode.goToSource(BreakpointNode.java:283)
        at
org.netbeans.modules.debugger.support.actions.GoToSourceAction.performAction(GoToSourceAction.java:39)
        at
org.openide.util.actions.NodeAction.actionPerformed(NodeAction.java:83)
        at org.netbeans.core.ModuleActions$1.run(ModuleActions.java:105)
        at org.openide.util.Task.run(Task.java:152)
[catch] at
org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:611)
Comment 1 _ ttran 2001-11-30 21:35:55 UTC
To bug reporter: which version of IDE/JDK/OS are you using?
Comment 2 John Baker 2001-11-30 21:50:17 UTC
Using Solaris JDK 1.3.1
Comment 3 Jesse Glick 2001-12-01 20:20:07 UTC
My guess: debuggercore is jumping to an invalidated source file that
it kept some reference to.

John: any other steps to reproduce? E.g. does this happen in a fresh
user directory? Or do you have to do something special such as save a
breakpoint and restart the IDE, or open the source file in the editor
and restart, or change the mount point of the samples directory, or
something similar...
Comment 4 Jan Jancura 2001-12-03 10:25:18 UTC
I can not reproduce it. Can you reproduce it with fresh directory,
please? This bug does not blocks any critical functionality P2 => P3.
Comment 5 Jan Chalupa 2001-12-03 13:21:33 UTC
Created attachment 3667 [details]
Exceptions stack-trace
Comment 6 Jan Chalupa 2001-12-03 13:27:21 UTC
I'm getting another NPE when executing the scenario described by the 
original submitter on the nb-release330-200111292300 build on W2K + 
Sun JDK 1.3.1_01 (clean userdir).

In Step 6, I need to double-click on the breakpoint node three times 
to get the exception. From that moment on every double-click brings 
the exception dialog up.

It's reliably reproducible on my machine and annoying -> P2.
Comment 7 Marian Petras 2001-12-04 02:56:35 UTC
The exception noted by Jan Chalupa was caused by bug #18017 which is
now fixed in branches 'release33' (since 2001/11/27 11:36:27 GMT) and
'release330' (since 2001/12/01 20:10:28 GMT). I have tested that
presence of the fix makes the difference.

The exception originally reported by John (jbaker@netbeans.org) cannot
be reproduced (as already reported by Jan Jancura) - probably fixed
together with another bug.
Comment 8 John Baker 2001-12-04 03:19:29 UTC
I can't reproduce this in kit 1203.  This has been fixed.
Thanks, John Baker