Eclipse Community Forums: Java Development Tools (JDT) » debugger stopping at a breakpoint that is not set

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » debugger stopping at a breakpoint that is not set

Show: Today's Messages :: Show Polls :: Message Navigator

debugger stopping at a breakpoint that is not set [message #260762]

Mon, 22 June 2009 18:17

Matt Morrisson

Messages: 3
Registered: July 2009

Junior Member

If I connect to my code with the debugger, eclipse will stop at a
breakpoint where no breakpoint is set (I have removed all breakpoints). It
will always break on the same line in the code. If I do not respond to the
break within a few seconds and hit resume (F8), then eclipse will pop-up
an error dialog with: "org.eclipse.jdi.TimeoutException: Timeout occurred
while waiting for packet nnnnn. occurred resuming thread." The remote VM
that I am debugging becomes unresponsive at this point and the VM process
has to be forcibly killed.

Stack for the thread that is hitting the breakpoints is:

Thread [Connection1] (Suspended (exeption ThreadDeath))
Connection.run() line: 114

The breakpoint is always hit in this class, Connection.java, on this
specific line. Line 114 is within a finally block. The finally block
calls into a "cleanup" method that closes a socket in addition to a few
other housekeeping functions.

My question then is, how do I continue to troubleshoot this problem so I
can not continually have eclipse break on this code when there is no
breakpoint there, and lock up the VM?

eclipse -debug output below. I also ran with -consolelog, but it didn't
seem to provide any addition useful info.

Start VM: -Xms40m
-Xmx256m
-XX:MaxPermSize=256m
-Djava.class.path=/home/mm/dev/eclipse/plugins/org.eclipse.e quinox.launcher_1.0.200.v20090306-1900.jar
-os linux
-ws gtk
-arch x86
-showsplash
/home/mm/dev/eclipse//plugins/org.eclipse.platform_3.3.200.v 200903130100/splash.bmp
-launcher /home/mm/dev/eclipse/eclipse
-name Eclipse
--launcher.library
/home/mm/dev/eclipse/plugins/org.eclipse.equinox.launcher.gt k.linux.x86_1.0.200.v20090306-1900/eclipse_1200.so
-startup
/home/mm/dev/eclipse/plugins/org.eclipse.equinox.launcher_1. 0.200.v20090306-1900.jar
-debug
-vm /home/mm/dev/jdk1.6.0_01/bin/../jre/lib/i386/client/libjvm.s o
-vmargs
-Xms40m
-Xmx256m
-XX:MaxPermSize=256m
-Djava.class.path=/home/mm/dev/eclipse/plugins/org.eclipse.e quinox.launcher_1.0.200.v20090306-1900.jar
Install location:
file:/home/mm/dev/eclipse/
Configuration file:
file:/home/mm/dev/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/mm/dev/eclipse/configuration/
Framework located:

file:/home/mm/dev/eclipse/plugins/org.eclipse.osgi_3.5.0.v20 090311-1300.jar
Framework classpath:

file:/home/mm/dev/eclipse/plugins/org.eclipse.osgi_3.5.0.v20 090311-1300.jar
Splash location:

/home/mm/dev/eclipse//plugins/org.eclipse.platform_3.3.200.v 200903130100/splash.bmp
Debug options:
file:/home/mm/dev/eclipse/.options not found
Time to load bundles: 6
Starting application: 2095
Application Started: 15582

Report message to a moderator

Re: debugger stopping at a breakpoint that is not set [message #260766 is a reply to message #260762]

Mon, 22 June 2009 18:51

Matt Morrisson

Messages: 3
Registered: July 2009

Junior Member

It looks like I missed this stack trace the first time I was running with
-consolelog turned on (included below). I'm not sure it is related, but it
seems likely, since it is coming through the JDIDebug code.

!ENTRY org.eclipse.jdt.debug 4 125 2009-06-22 10:51:10.542
!MESSAGE Internal error logged from JDI Debug:
!STACK 0
org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for
packet 738.
at
org.eclipse.jdi.internal.connect.PacketReceiveManager.getRep ly(PacketReceiveManager.java:171)
at
org.eclipse.jdi.internal.connect.PacketReceiveManager.getRep ly(PacketReceiveManager.java:180)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:174)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:230)
at
org.eclipse.jdi.internal.VirtualMachineImpl.dispose(VirtualM achineImpl.java:635)
at
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.dis connect(JDIDebugTarget.java:706)
at
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.shu tdown(JDIDebugTarget.java:1545)
at
org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.stop(JDID ebugPlugin.java:296)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:865)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:858)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:474)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.susp end(AbstractBundle.java:546)
at
org.eclipse.osgi.framework.internal.core.Framework.suspendBu ndle(Framework.java:1123)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d ecFWSL(StartLevelManager.java:593)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:261)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.s hutdown(StartLevelManager.java:216)
at
org.eclipse.osgi.framework.internal.core.InternalSystemBundl e.suspend(InternalSystemBundle.java:266)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:685)
at
org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:583)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:409)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:200)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 556)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
at org.eclipse.equinox.launcher.Main.run(Main.java:1284)

Report message to a moderator

Re: debugger stopping at a breakpoint that is not set [message #260788 is a reply to message #260766]

Wed, 24 June 2009 21:39

Will Horn

Messages: 265
Registered: July 2009

Senior Member

Have you checked in Preferences, Java\Debug, "Suspend execution on uncaught
exceptions"?

It looks like something is throwing an uncaught ThreadDeath error.

"Matt Morrisson" <mmorrisson@gmail.com> wrote in message
news:df7efaf59e647ed54adcd5c3d970ed0d$1@www.eclipse.org...
> It looks like I missed this stack trace the first time I was running
> with -consolelog turned on (included below). I'm not sure it is related,
> but it seems likely, since it is coming through the JDIDebug code.
>
>
> !ENTRY org.eclipse.jdt.debug 4 125 2009-06-22 10:51:10.542
> !MESSAGE Internal error logged from JDI Debug: !STACK 0
> org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for
> packet 738.
> at
> org.eclipse.jdi.internal.connect.PacketReceiveManager.getRep ly(PacketReceiveManager.java:171)
> at
> org.eclipse.jdi.internal.connect.PacketReceiveManager.getRep ly(PacketReceiveManager.java:180)
> at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:174)
> at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:230)
> at
> org.eclipse.jdi.internal.VirtualMachineImpl.dispose(VirtualM achineImpl.java:635)
> at
> org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.dis connect(JDIDebugTarget.java:706)
> at
> org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.shu tdown(JDIDebugTarget.java:1545)
> at
> org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.stop(JDID ebugPlugin.java:296)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:865)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:858)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:474)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.susp end(AbstractBundle.java:546)
> at
> org.eclipse.osgi.framework.internal.core.Framework.suspendBu ndle(Framework.java:1123)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ecFWSL(StartLevelManager.java:593)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:261)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.s hutdown(StartLevelManager.java:216)
> at
> org.eclipse.osgi.framework.internal.core.InternalSystemBundl e.suspend(InternalSystemBundle.java:266)
> at
> org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:685)
> at
> org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:583)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:409)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:200)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 556)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
>
>
>

Report message to a moderator

Re: debugger stopping at a breakpoint that is not set [message #260791 is a reply to message #260788]

Wed, 24 June 2009 23:42

Matt Morrisson

Messages: 3
Registered: July 2009

Junior Member

Will Horn wrote:

> Have you checked in Preferences, Java->Debug, "Suspend execution on uncaught
> exceptions"?

> It looks like something is throwing an uncaught ThreadDeath error.

I wasn't aware of that setting. Unselecting "Suspend execution on uncaught
exceptions" does prevent the debugger from stopping in this case. Thanks
for pointing that out.

Report message to a moderator

Previous Topic:	Track an Object
Next Topic:	overriden method causes compile error "indirectly referenced"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jul 13 19:22:46 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter