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 182127 - [69cat] org.netbeans.api.debugger.jpda.InvalidExpressionException: No current context (stack frame)
Summary: [69cat] org.netbeans.api.debugger.jpda.InvalidExpressionException: No current...
Status: CLOSED DUPLICATE of bug 181752
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-16 15:01 UTC by Egor Ushakov
Modified: 2010-05-10 08:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 166341

Attachments
stacktrace (1.72 KB, text/plain)
2010-03-16 15:01 UTC, Egor Ushakov 		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 Egor Ushakov 2010-03-16 15:01:07 UTC 
Build: NetBeans IDE Dev (Build 201003140200)
VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07
OS: SunOS

User Comments:
gorrus: did step in the debugger

gholmer: Stepping through code in the debugger (F8).




Stacktrace: 
org.netbeans.api.debugger.jpda.InvalidExpressionException: No current context (stack frame)
   at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.evaluateGeneric(JPDADebuggerImpl.java:768)
   at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.evaluate(JPDADebuggerImpl.java:338)
   at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.evaluate(JPDADebuggerImpl.java:314)
   at org.netbeans.modules.debugger.jpda.models.AbstractObjectVariable.evaluate(AbstractObjectVariable.java:531)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:0)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Comment 1 Egor Ushakov 2010-03-16 15:01:11 UTC 
Created attachment 95242 [details]
stacktrace
Comment 2 Martin Entlicher 2010-03-16 15:36:34 UTC 

*** This bug has been marked as a duplicate of bug 181752 ***
Comment 3 Marian Mirilovic 2010-05-10 08:50:36 UTC 
verified duplicate