Community
Participate
Working Groups
The following incident was reported via the automated error reporting: code: 125 plugin: org.eclipse.jdt.debug_3.8.0.v20130514-0841 message: Internal error logged from JDI Debug: fingerprint: 89d836cb exception class: org.eclipse.jdi.TimeoutException exception message: Timeout occurred while waiting for packet 32. number of children: 0 org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 32. at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:186) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:197) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:226) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:242) at org.eclipse.jdi.internal.ThreadReferenceImpl.status(ThreadReferenceImpl.java:473) at org.eclipse.jdt.internal.debug.core.model.JDIThread.initialize(JDIThread.java:328) at org.eclipse.jdt.internal.debug.core.model.JDIThread.<init>(JDIThread.java:264) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.newThread(JDIDebugTarget.java:562) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createThread(JDIDebugTarget.java:538) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.initializeState(JDIDebugTarget.java:492) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.initialize(JDIDebugTarget.java:447) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.<init>(JDIDebugTarget.java:315) at org.eclipse.jdt.debug.core.JDIDebugModel$1.run(JDIDebugModel.java:183) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget(JDIDebugModel.java:187) at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget(JDIDebugModel.java:135) at org.eclipse.jdt.internal.launching.SocketAttachConnector.connect(SocketAttachConnector.java:143) at org.eclipse.jdt.internal.launching.JavaRemoteApplicationLaunchConfigurationDelegate.launch(JavaRemoteApplicationLaunchConfigurationDelegate.java:84) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) General Information: reported-by: . anonymous-id: a3884418-1cf1-4823-969c-f63641b37576 eclipse-build-id: 4.3.2.M20140221-1700 eclipse-product: org.eclipse.epp.package.cpp.product operating system: MacOSX 10.10.1 (x86_64) - cocoa jre-version: 1.8.0_20-b26 The following plug-ins were present on the execution stack (*): 1. org.eclipse.core.jobs_3.5.300.v20130429-1813 2. org.eclipse.core.resources_3.8.101.v20130717-0806 3. org.eclipse.debug.core_3.8.0.v20130514-0954 4. org.eclipse.debug.ui_3.9.0.v20130516-1713 5. org.eclipse.jdt.debug_3.8.0.v20130514-0841 6. org.eclipse.jdt_3.9.1.v20140221-1700 7. org.eclipse.jdt.launching_3.7.1.v20131218-1102 Please note that: * Messages, stacktraces, and nested status objects may be shortened. * Bug fields like status, resolution, and whiteboard are sent back to reporters. * The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality. Other Resources: * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/54f833ace4b0ad909161a98b * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide Thank you for your assistance. Your friendly error-reports-inbox.
*** This bug has been marked as a duplicate of bug 94452 ***