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 81754 - Steping (F8) in the debugger causes
Summary: Steping (F8) in the debugger causes
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2006-08-02 23:39 UTC by wrongway
Modified: 2010-04-29 09:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 wrongway 2006-08-02 23:39:55 UTC 
java.lang.IllegalThreadStateException
	at com.sun.tools.jdi.JDWPException.toJDIException
(JDWPException.java:45)
	at com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.set
(EventRequestManagerImpl.java:181)
	at 
com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.setEnabled
(EventRequestManagerImpl.java:142)
	at com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.enable
(EventRequestManagerImpl.java:127)
	at 
org.netbeans.modules.debugger.jpda.actions.StepActionProvider.runAction
(StepActionProvider.java:136)
	at org.netbeans.modules.debugger.jpda.actions.StepActionProvider$1.run
(StepActionProvider.java:107)
	at 
org.netbeans.modules.debugger.jpda.actions.JPDADebuggerActionProvider$1.run
(JPDADebuggerActionProvider.java:150)
	at org.openide.util.RequestProcessor$Task.run
(RequestProcessor.java:499)
[catch] at org.openide.util.RequestProcessor$Processor.run
(RequestProcessor.java:932)
Comment 1 Jiri Kovalsky 2006-08-03 09:45:24 UTC 
Is it reproducible wrongway ? We would appreciate if you provide us with some
steps to invoke this malfunction. Does it actually step when the exception is
thrown or what are the consequences ?
Comment 2 wrongway 2006-08-03 21:27:44 UTC 
It only happened once.  Have not seen it since that time.  No, I had to reboot 
the app.
Comment 3 Martin Entlicher 2006-08-04 10:08:50 UTC 
It's some race condition, it's likely unreproducible. We'll hopefully find the
missing synchronization.....
Comment 4 Roman Ondruska 2007-06-25 17:09:23 UTC 
Not reproducible with NB 6, however, still not closing it. P3->P4
Comment 5 Martin Entlicher 2008-09-18 22:40:46 UTC 
Since this does not seems to occur in 6.5 builds, it was likely already fixed.
Please reopen if it reappears with steps to reproduce, if possible.
Comment 6 Quality Engineering 2010-04-29 09:29:46 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.