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 95083 - [tests] Thread breakpoint test failed by InterruptedException
Summary: [tests] Thread breakpoint test failed by InterruptedException
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 105516 117541 119262 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-09 14:30 UTC by ehucka
Modified: 2007-10-19 14:31 UTC (History)
0 users

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 ehucka 2007-02-09 14:30:22 UTC
Automated test gui.debuggercore.Breakpoints.testThreadBreakpointFunctionality
from debuggercore/test/qa-functional randomaly fails by InterruptedException.

Test creates Thread breakpoint with default settings, start debugging, invoke
Continue two times after debugger stops on "Thread breakpoint hit by thread ..."
and waits for 'User program running' state.

java.lang.InterruptedException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:474)
	at java.awt.EventQueue.invokeAndWait(EventQueue.java:848)
	at javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1257)
	at
org.netbeans.modules.debugger.jpda.projects.EditorContextImpl.getCurrentLineNumber(EditorContextImpl.java:350)
	at
org.netbeans.modules.debugger.jpda.ui.EditorContextBridge.getCurrentLineNumber(EditorContextBridge.java:143)
	at
org.netbeans.modules.debugger.jpda.ui.actions.RunToCursorActionProvider.actionStateChanged(RunToCursorActionProvider.java:136)
	at
org.netbeans.api.debugger.ActionsManager.fireActionStateChanged(ActionsManager.java:373)
	at org.netbeans.api.debugger.ActionsManager.access$400(ActionsManager.java:37)
	at
org.netbeans.api.debugger.ActionsManager$MyActionListener.actionStateChange(ActionsManager.java:478)
	at
org.netbeans.spi.debugger.ActionsProviderSupport.fireActionStateChanged(ActionsProviderSupport.java:86)
	at
org.netbeans.spi.debugger.ActionsProviderSupport.setEnabled(ActionsProviderSupport.java:73)
	at
org.netbeans.modules.debugger.jpda.actions.ContinueActionProvider.checkEnabled(ContinueActionProvider.java:86)
	at
org.netbeans.modules.debugger.jpda.actions.JPDADebuggerActionProvider.propertyChange(JPDADebuggerActionProvider.java:75)
	at
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:333)
	at
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:341)
	at
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:270)
	at
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.firePropertyChange(JPDADebuggerImpl.java:1039)
	at
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.setState(JPDADebuggerImpl.java:1026)
	at
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.setStoppedState(JPDADebuggerImpl.java:830)
	at
org.netbeans.modules.debugger.jpda.breakpoints.BreakpointImpl.perform(BreakpointImpl.java:249)
	at
org.netbeans.modules.debugger.jpda.breakpoints.ThreadBreakpointImpl.exec(ThreadBreakpointImpl.java:93)
	at org.netbeans.modules.debugger.jpda.util.Operator$1.run(Operator.java:209)
	at java.lang.Thread.run(Thread.java:595)
Comment 1 Martin Entlicher 2007-02-14 17:14:08 UTC
It looks like the debugger session has finished sooner then all the action state
changes were processed. A similar issue (issue #90443) was already fixed.
Comment 2 Martin Entlicher 2007-06-06 19:01:16 UTC
*** Issue 105516 has been marked as a duplicate of this issue. ***
Comment 3 Martin Entlicher 2007-06-06 19:02:48 UTC
A very similar exception is reported in issue #105516. The fix should cover both.
Comment 4 Martin Entlicher 2007-10-03 16:13:50 UTC
*** Issue 117541 has been marked as a duplicate of this issue. ***
Comment 5 Martin Entlicher 2007-10-17 23:25:18 UTC
*** Issue 119262 has been marked as a duplicate of this issue. ***
Comment 6 Martin Entlicher 2007-10-18 16:42:56 UTC
We must not call thread.interrupt() when the thread process some foreign code.
It's fixed in trunk:

/shared/data/ccvs/repository/debuggerjpda/src/org/netbeans/modules/debugger/jpda/util/Operator.java,v  <--  Operator.java
new revision: 1.51; previous revision: 1.50
Comment 7 ehucka 2007-10-19 14:31:09 UTC
verified