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 205642 - [71cat] com.sun.jdi.InvalidStackFrameException: Thread has been resumed
Summary: [71cat] com.sun.jdi.InvalidStackFrameException: Thread has been resumed
Status: RESOLVED DUPLICATE of bug 205635
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-29 10:28 UTC by williambacchi
Modified: 2012-05-31 14:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 183269

Attachments
stacktrace (2.86 KB, text/plain)
2011-11-29 10:28 UTC, williambacchi 		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 williambacchi 2011-11-29 10:28:21 UTC 
This bug was originally marked as duplicate of bug 175699, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.1 RC1 (Build 201111242103)
VM: Java HotSpot(TM) Client VM, 17.1-b03, Java(TM) SE Runtime Environment, 1.6.0_22-b04
OS: Windows XP

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.location(StackFrameImpl.java:71)
   at com.sun.tools.jdi.LocalVariableImpl.isVisible(LocalVariableImpl.java:102)
   at com.sun.tools.jdi.StackFrameImpl.createVisibleVariables(StackFrameImpl.java:148)
   at com.sun.tools.jdi.StackFrameImpl.visibleVariableByName(StackFrameImpl.java:178)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.getIdentifierByName(EvaluatorVisitor.java:1693)
Comment 1 williambacchi 2011-11-29 10:28:23 UTC 
Created attachment 113608 [details]
stacktrace
Comment 2 Martin Entlicher 2012-05-31 14:13:21 UTC 
This is in fact the same problem as issue #205635.

*** This bug has been marked as a duplicate of bug 205635 ***