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.
Build: NetBeans IDE Dev (Build 200809220201) VM: Java HotSpot(TM) Client VM, 11.0-b15, Java(TM) SE Runtime Environment, 1.6.0_10-rc-b28 OS: Windows XP, 5.1, x86 User Comments: ulfzibis: Clicked on Debugger Watches tab. See: Issue 148377 Stacktrace: java.lang.IllegalStateException at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.evaluateIn(JPDADebuggerImpl.java:832) at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.evaluateIn(JPDADebuggerImpl.java:664) at org.netbeans.modules.debugger.jpda.models.WatchesModel$JPDAWatchEvaluating.getValue(WatchesModel.java:394) at org.netbeans.modules.debugger.jpda.models.WatchesModel$JPDAWatchEvaluating.getType(WatchesModel.java:363) at org.netbeans.modules.debugger.jpda.ui.models.VariablesTreeModelFilter.getFilter(VariablesTreeModelFilter.java:473) at org.netbeans.modules.debugger.jpda.ui.models.VariablesTreeModelFilter.access$100(VariablesTreeModelFilter.java:78)
Created attachment 70598 [details] stacktrace
*** Issue 148408 has been marked as a duplicate of this issue. ***
I'm going to look at this. Looks like some synchronization problem...
There's something strange going on there. All duplicate issues contain stack traces where IncompatibleThreadStateException is thrown at TreeEvaluator.evaluate(TreeEvaluator.java:105) from "frameThread.frames()" expression. But the "frameThread" is taken from "frame.thread()" call, which succeeds. This seems to indicate that the thread was suspended when we called "frame.thread()" on line 104 and unsuspended when we call "frameThread.frames()" on line 105. It's almost impossible from probability point of view for this to happen consistently several times at the same point. There must be something more in it...
I was not able to reproduce this yet. Adding RANDOM keyword, since there are no deterministic steps to reproduce AFAIK. I've occasionally got "No current context" message in the watches, but no exception.
cyb3r, do you have some concrete steps to reproduce?
Thank you for report! We are not able to reproduce the described problem. Informations you've provided aren't enough to fix the issue. You haven't added comment with steps to reproduce/system info/messages.log to the issue as requested. We are closing as worksforme for now. Please, add requested informations and reopen it if you are still able to reproduce this issue. Thanks in advance.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.