Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313343

Summary:	InternalException on Hotcode Replacement
Product:	[Eclipse Project] JDT	Reporter:	Heiko Böttger <heiko.boettger>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	darin.eclipse
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Heiko Böttger

2010-05-18 09:05:39 EDT

Build Identifier: 20100218-1602

com.sun.jdi.InternalException: Got error code in reply:23
at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler(MirrorImpl.java:261)
at org.eclipse.jdi.internal.ReferenceTypeImpl.methods(ReferenceTypeImpl.java:1014)
at org.eclipse.jdi.internal.ReferenceTypeImpl.locationsOfLine(ReferenceTypeImpl.java:1451)
at org.eclipse.jdi.internal.ReferenceTypeImpl.locationsOfLine(ReferenceTypeImpl.java:996)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.determineLocations(JavaLineBreakpoint.java:311)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.newRequests(JavaLineBreakpoint.java:256)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.createRequest(JavaBreakpoint.java:442)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.createRequests(JavaBreakpoint.java:568)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.addToTarget(JavaBreakpoint.java:532)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.addToTarget(JavaLineBreakpoint.java:161)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.breakpointAdded(JDIDebugTarget.java:1192)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.reinstallBreakpointsIn(JDIDebugTarget.java:852)
at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.redefineTypesJDK(JavaHotCodeReplaceManager.java:592)
at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.doHotCodeReplace(JavaHotCodeReplaceManager.java:457)
at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.access$0(JavaHotCodeReplaceManager.java:417)
at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager$1.run(JavaHotCodeReplaceManager.java:306)
at org.eclipse.debug.core.DebugPlugin$AsynchRunner.run(DebugPlugin.java:1040)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.debug.core.DebugPlugin$AsynchRunner.async(DebugPlugin.java:1023)
at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:380)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)


Reproducible: Couldn't Reproduce

Steps to Reproduce:
This happens here quite often, but I cannot find a reliable way to reproduce it. After this exception the debugged application hangs and I have to use the stop button.

Comment 1 Darin Wright

2010-05-18 14:22:18 EDT

Error code 23 indicates "INVALID_MEHTODID". However, in this case, we're asking the VM for all methods in a reference type, and that return code is not spec'd to be one of the possible/expected return codes.

A reproduceable test case would help, or you may want to see if using a newer VM avoids the problem.

http://java.sun.com/javase/6/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_Error

Comment 2 Eclipse Genie

2020-03-01 17:43:45 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.