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 220423 - com.sun.jdi.InternalException: Unexpected JDWP Error: 113
Summary: com.sun.jdi.InternalException: Unexpected JDWP Error: 113
Status: RESOLVED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-19 13:44 UTC by mstarnacki
Modified: 2012-10-20 11:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 193773


Attachments
stacktrace (1.69 KB, text/plain)
2012-10-19 13:44 UTC, mstarnacki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mstarnacki 2012-10-19 13:44:54 UTC
Build: NetBeans IDE Dev (Build 201210180002)
VM: Java HotSpot(TM) Client VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b10
OS: Linux

User Comments:
mstarnacki: Debug jar application on the remote machine. I have had 1 brake point selected.




Stacktrace: 
com.sun.jdi.InternalException: Unexpected JDWP Error: 113
   at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:65)
   at com.sun.tools.jdi.ObjectReferenceImpl.invokeMethod(ObjectReferenceImpl.java:397)
   at org.netbeans.modules.debugger.jpda.jdi.ObjectReferenceWrapper.invokeMethod(ObjectReferenceWrapper.java:510)
   at org.netbeans.modules.debugger.jpda.visual.RemoteServices.uploadBasicClasses(RemoteServices.java:164)
   at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener.initDebuggerRemoteService(VisualDebuggerListener.java:256)
   at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener.access$100(VisualDebuggerListener.java:122)
Comment 1 mstarnacki 2012-10-19 13:44:57 UTC
Created attachment 126195 [details]
stacktrace
Comment 2 Martin Entlicher 2012-10-20 11:38:19 UTC
Error 113 is "An unexpected internal error has occurred."
I do not think we can do anything about this. If you have some concrete steps to reproduce, we can submit a bug for JDK.