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 179469 - NullPointerException at com.sun.tools.jdi.ReferenceTypeImpl.visibleFields
Summary: NullPointerException at com.sun.tools.jdi.ReferenceTypeImpl.visibleFields
Status: CLOSED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-13 12:45 UTC by dvd76
Modified: 2010-05-19 08:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 80005

Attachments
stacktrace (1.98 KB, text/plain)
2010-01-13 12:45 UTC, dvd76 		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 dvd76 2010-01-13 12:45:10 UTC 
Build: NetBeans IDE 6.7.1 (Build 200907230233)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86

User Comments:
dvd76: can't see variable value during debug

GUEST: On-device debugging of a midlet on a Sony Ericsson mobile (W910i) using the Sony Ericsson SDK (v2.5.0).



Stacktrace: 
java.lang.NullPointerException
   at com.sun.tools.jdi.ReferenceTypeImpl.visibleFields(ReferenceTypeImpl.java:380)
   at com.sun.tools.jdi.ReferenceTypeImpl.fieldByName(ReferenceTypeImpl.java:428)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.visitIdentifier(EvaluatorVisitor.java:1697)
   at org.netbeans.modules.debugger.jpda.expr.EvaluatorVisitor.visitIdentifier(EvaluatorVisitor.java:182)
   at com.sun.tools.javac.tree.JCTree$JCIdent.accept(JCTree.java:1689)
   at com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:49)
Comment 1 dvd76 2010-01-13 12:45:14 UTC 
Created attachment 93262 [details]
stacktrace
Comment 2 Martin Entlicher 2010-01-14 01:24:55 UTC 
We can not do anything about this, this is a JDI defect (or debugger backend defect). I'll submit a bug for JDK. Please provide steps to reproduce - what you were evaluating and some sample code.
Comment 3 Marian Mirilovic 2010-05-19 08:59:15 UTC 
Agreed with Martin - closed