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 253312 - InternalError: Location with invalid code index
Summary: InternalError: Location with invalid code index
Status: RESOLVED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-05 22:38 UTC by jcrada
Modified: 2015-07-14 11:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 183802

Attachments
stacktrace (1.14 KB, text/plain)
2015-07-05 22:38 UTC, jcrada 		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 jcrada 2015-07-05 22:38:04 UTC 
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: OpenJDK 64-Bit Server VM, 24.79-b02, OpenJDK Runtime Environment, 1.7.0_79-b14
OS: Linux

User Comments:
GUEST: During Profiling a java application

jcrada: Debugging focused Test method in Java App




Stacktrace: 
java.lang.InternalError: Location with invalid code index
   at com.sun.tools.jdi.ConcreteMethodImpl.codeIndexToLineInfo(ConcreteMethodImpl.java:182)
   at com.sun.tools.jdi.LocationImpl.getBaseLineInfo(LocationImpl.java:126)
   at com.sun.tools.jdi.LocationImpl.getLineInfo(LocationImpl.java:140)
   at com.sun.tools.jdi.LocationImpl.sourceName(LocationImpl.java:191)
   at com.sun.tools.jdi.LocationImpl.sourceName(LocationImpl.java:186)
   at org.netbeans.modules.debugger.jpda.jdi.LocationWrapper.sourceName(LocationWrapper.java:574)
Comment 1 jcrada 2015-07-05 22:38:06 UTC 
Created attachment 154489 [details]
stacktrace
Comment 2 Martin Entlicher 2015-07-10 16:02:19 UTC 
Looks like a defect in JDI.
Do you have some specific steps to reproduce?
Comment 3 Martin Entlicher 2015-07-14 11:53:25 UTC 
I was not able to reproduce, or find what is causing the error.
It looks like a JDI issue, if you provide steps to reproduce, I could submit a defect for JDI. Or please submit the problem directly for the JDK.