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 191224 - com.sun.jdi.InvalidStackFrameException: Thread has been resumed
Summary: com.sun.jdi.InvalidStackFrameException: Thread has been resumed
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P4 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-21 14:49 UTC by Vladimir Voskresensky
Modified: 2011-11-16 10:28 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 172593

Attachments
stacktrace (3.99 KB, text/plain)
2010-10-21 14:49 UTC, Vladimir Voskresensky 		Details
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 Vladimir Voskresensky 2010-10-21 14:49:43 UTC 
This issue was reported manually by vv159170.
It already has 2 duplicates 


Build: NetBeans IDE Dev (Build 101020-b547b421726d)
VM: Java HotSpot(TM) Client VM, 17.0-b16, Java(TM) SE Runtime Environment, 1.6.0_21-b06
OS: Linux

User Comments:
vv159170: stopped on two breakpoints in two different threads




Stacktrace: 
com.sun.jdi.InvalidStackFrameException: Thread has been resumed
   at com.sun.tools.jdi.StackFrameImpl.validateStackFrame(StackFrameImpl.java:62)
   at com.sun.tools.jdi.StackFrameImpl.thisObject(StackFrameImpl.java:101)
   at org.netbeans.modules.debugger.jpda.expr.EvaluationContext.getContextObject(EvaluationContext.java:164)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.visitMethodInvocation(EvaluatorVisitor.java:354)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.visitMethodInvocation(EvaluatorVisitor.java:192)
   at com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1341)
Comment 1 Vladimir Voskresensky 2010-10-21 14:49:52 UTC 
Created attachment 102546 [details]
stacktrace
Comment 2 Martin Entlicher 2010-10-26 06:59:13 UTC 
I'm not able to reproduce this. It seems to occur quite rarely, moving to P4...
Comment 3 Martin Entlicher 2011-11-16 10:28:38 UTC 
This should be fixed by changeset:   207331:17116257a6b8
http://hg.netbeans.org/main/rev/17116257a6b8