| debugger stopping at a breakpoint that is not set [message #260762] |
Mon, 22 June 2009 14:17  |
Eclipse User |
|
|
|
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
|
|
|
|
|
| Re: debugger stopping at a breakpoint that is not set [message #260791 is a reply to message #260788] |
Wed, 24 June 2009 19:42  |
| Eclipse User |
|
|
|
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.
|
|
|
Powered by
FUDForum. Page generated in 0.04365 seconds
Home