Eclipse debugging hanging, causing network problems
- From: kohomban@xxxxxxxxx
- Date: 3 Oct 2006 19:21:15 -0700
Hi,
I'm new to Eclipese, and last time I used Java heavily was six years
ago, so may be new to Java as well.
I could install and run Eclipse well, but debugging gives a problem;
after a few (say, 5-10) debugging sessions, the debugger does not
start in the usual way, but gets stuck at launching stage. The status
bar shows "Launching (95%)" and takes minutes to continue from there.
The app is a local java program, very small stuff - a couple of seconds
to run, no network connections etc. If I let the IDE to get past the
launching stage it gives me a debug session, but its either stuck
without running, or extremely slow to run.
Strangely, after this happens, I get other network problems as well -
such as google toolbar (in firefox) being slow to respond etc; The only
remedy is to reboot the machine, and when rebooting, several network
related apps fail to close down and I have to terminate them. I believe
I have reasonably verified that the cause is not an independent network
issue but something associated with the debugger.
..metadata/.log file shows many errors associated with
org.eclipse.jdi.internal, including org.eclipse.jdi.TimeOutException s.
My questions:
1. is this issue known (although I couldn't see anything on the web)
and if so, how can I fix it?
2. Can I setup eclipse to use shared memory transport instead of socket
transport for debugging?
Thanks for your time,
Upali
.
- Prev by Date: Re: Ask the experts session on Swing (October 16-20)
- Next by Date: Eclipse Debugger Skipping Code
- Previous by thread: Ask the experts session on Swing (October 16-20)
- Next by thread: Eclipse Debugger Skipping Code
- Index(es):
Relevant Pages
|
