Community
Participate
Working Groups
* Place a line breakpoint on first line of VectorTest#testCapacity() * Debug to breakpoint (using jdk1.4.1) * Place an instance watchpoint on "fFull" * (re)launch 2nd target - resume when it hits the line breakpoint * the 2nd target exits as expected * (re)launch a 3rd target - Got the following exception while launching * resume the 1st target - it resumes and exists, while it should stop at watchpoint. !ENTRY org.eclipse.debug.ui 4 5013 Sep 17, 2002 08:58:23.782 !MESSAGE Exception occurred while launching !STACK 0 com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:123) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:137) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:167) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:185) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:215) at org.eclipse.jdi.internal.ReferenceTypeImpl.signature (ReferenceTypeImpl.java:809) at org.eclipse.jdi.internal.ReferenceTypeImpl.name (ReferenceTypeImpl.java:795) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.getTypeName (JavaBreakpoint.java:732) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.addToTarget (JavaBreakpoint.java:415) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.breakpointAdded (JDIDebugTarget.java:999) at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.notifyTarget (JavaDebugOptionsManager.java:360) at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.handleDebugEvents (JavaDebugOptionsManager.java:563) at org.eclipse.debug.core.DebugPlugin.fireDebugEventSet (DebugPlugin.java:242) at org.eclipse.jdt.internal.debug.core.model.JDIDebugElement.fireEvent (JDIDebugElement.java:133) at org.eclipse.jdt.internal.debug.core.model.JDIDebugElement.fireCreationEvent (JDIDebugElement.java:123) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.initialize (JDIDebugTarget.java:338) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.<init> (JDIDebugTarget.java:237) at org.eclipse.jdt.debug.core.JDIDebugModel$1.run (JDIDebugModel.java:134) at org.eclipse.core.internal.resources.Workspace.run (Workspace.java:1361) at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget (JDIDebugModel.java:138) at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget (JDIDebugModel.java:98) at org.eclipse.jdt.internal.launching.StandardVMDebugger.run (StandardVMDebugger.java:145) at org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunchConfigurationDelega te.launch(JavaLocalApplicationLaunchConfigurationDelegate.java:97) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConfiguration.java:140) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog$11. run(LaunchConfigurationDialog.java:2269) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run (ModalContext.java:98)
Fixed. The problem was that the 2nd target attempted to add an instance filter for an object in a different VM. I changed the implementation for instance filters - adding the infrastructure at the IJavaBreakpoint level. The UI still only reveals the feature on watchpoints, but we can enhance this. Current side effect is that instance watchpoints become "global" watchpoints after a target terminates.
Please verify, Jared B.
This is actually a dup.
*** This bug has been marked as a duplicate of 23423 ***
