|
Re: Debug Error: Cannot Connect to VM [message #505060 is a reply to message #504852] |
Fri, 25 December 2009 23:55 |
Eclipse User |
|
|
|
Originally posted by: gunnar.stahl.gunnarstahl.org
Hi, ran into a similar problem today. On debian testing the Java networking was completely disabled. Check out the following URL if you use debian testing:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056
Yt, Gunnar
erickulcyk@gmail.com schrieb:
> I get this error when I try to debug any application
>
> Cannot connect to VM
>
> com.sun.jdi.connect.TransportTimeoutException
> at org.eclipse.jdi.internal.connect.SocketTransportService.acce
> pt(SocketTransportService.java:97)
> at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(
> SocketTransportImpl.java:56)
> at org.eclipse.jdi.internal.connect.SocketListeningConnectorImp
> l.accept(SocketListeningConnectorImpl.java:135)
> at org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec
> tRunnable.run(StandardVMDebugger.java:107)
> at java.lang.Thread.run(Thread.java:636)
>
> Then on the terminal I get this:
>
> ERROR: transport error 202: connect failed: Connection timed out
> ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
> initialized [../../../src/share/back/debugInit.c:690]
> FATAL ERROR in native method: JDWP No transports initialized,
> jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
>
> As far as I can tell, my debug and run configurations are exactly the
> same (they use the same VM). What could be the problem?
>
> Thanks,
> Eric
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.08981 seconds