Title: JDEBug vs Win2K and/or NT4: Status?
Hi all,
I see in the mail-traffic that Paul K has changed the JDEBug code to avoid
setting priority on the thread when launching the debuggee process, in an
effort to cure the problems with deadlocking at launch.
What has not appeared is any user
Title: JDEBug vs Win2K and/or NT4: Status?
The timeout problem still happens to me on
Windows 2000 SP1. It does not happen on Windows 2000 without
SP1.
In the Messages buffer: No response to command 1.
(process = 1; timeout = 30 sec.)
At this point,
it's pretty much dead. There is a javaw
]
Sent: Friday, April 27, 2001 11:48 AM
Subject: RE: JDEBug vs Win2K and/or NT4: Status?
At 11:10 AM 4/27/01 -0400, Javier Lopez wrote:
I tried it on simple class, (JDE-Debug App)
and I get something like
Error: debugger didn't respond to command:
-1 2607 launch 12 -vmexec javaw
to port 1900.
Any thoughts as to why this might be happening?
- Paul
Javier
-Original Message-
From: Jim Goodwin [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 10:55 AM
To: '[EMAIL PROTECTED]'
Subject: JDEBug vs Win2K and/or NT4: Status?
Hi all
-
From: Jim Goodwin [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 10:55 AM
To: '[EMAIL PROTECTED]'
Subject: JDEBug vs Win2K and/or NT4: Status?
Hi all,
I see in the mail-traffic that Paul K has changed the JDEBug code to
avoid
setting priority on the thread when
