364117 – org.eclipse.jdi.TimeoutException while debug android application

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

Bug 364117 - org.eclipse.jdi.TimeoutException while debug android application

Summary: org.eclipse.jdi.TimeoutException while debug android application

Status:	CLOSED DUPLICATE of bug 217962

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Debug (show other bugs)
Version:	4.2
Hardware:	PC Windows 7

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Debug-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-11-18 03:41 EST by Igor
Modified:	2012-05-11 12:47 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
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 Igor

2011-11-18 03:41:20 EST

Build Identifier: M20110210-1200

I get looped org.eclipse.jdi.TimeoutException while debugging android application.

org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 3643.
	at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:171)
	at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:180)
	at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:174)
	at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:192)
	at org.eclipse.jdi.internal.VirtualMachineImpl.classesBySignature(VirtualMachineImpl.java:599)
	at org.eclipse.jdi.internal.VirtualMachineImpl.classesByName(VirtualMachineImpl.java:626)
	at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.jdiClassesByName(JDIDebugTarget.java:1510)
	at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.filterUnloadedTypes(JavaHotCodeReplaceManager.java:338)
	at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.notifyUnsupportedHCR(JavaHotCodeReplaceManager.java:364)
	at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager$2.run(JavaHotCodeReplaceManager.java:318)
	at org.eclipse.debug.core.DebugPlugin$AsynchRunner.run(DebugPlugin.java:1048)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.debug.core.DebugPlugin$AsynchRunner.async(DebugPlugin.java:1031)
	at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:388)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Reproducible: Didn't try

Comment 1 Remy Suen

2011-11-18 09:34:11 EST

Is this 100% reproducible? Can you debug regular Java applications?

Comment 2 Igor

2011-11-18 11:37:56 EST

(In reply to comment #1)
> Is this 100% reproducible? Can you debug regular Java applications?

the problem reproducible occasionally after stopping on breakpoints and being stopped for some time.

Currently I work on Android apps only.

Comment 3 Michael Rennie

2012-05-11 12:47:06 EDT


*** This bug has been marked as a duplicate of bug 217962 ***