Re: JDEBug vs Win2K and/or NT4: Status?

2001-05-08 Thread Paul Kinnucan
- Original Message - From: "Javier Lopez" <[EMAIL PROTECTED]> To: "John L. Utz III" <[EMAIL PROTECTED]>; "Paul Kinnucan" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, May 08, 2001 2:33 PM Subject: RE: JDEBug vs Win2K and/

RE: JDEBug vs Win2K and/or NT4: Status?

2001-05-08 Thread Javier Lopez
ng to the process. Javier -Original Message- From: John L. Utz III [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 08, 2001 1:01 PM To: Paul Kinnucan Cc: [EMAIL PROTECTED] Subject: RE: JDEBug vs Win2K and/or NT4: Status? hi paul; i have time to work on this again over the next few

RE: JDEBug vs Win2K and/or NT4: Status?

2001-05-08 Thread John L. Utz III
hi paul; i have time to work on this again over the next few days here is the current error message with beta11 on my win2k sp1 box *** Debugger Output for Process com.singingfish.cpp.apps.xmlValidator(2) *** Launched VM Java Debug Interface (Reference Implementation) version 1.3 Java Debu

RE: JDEBug vs Win2K and/or NT4: Status?

2001-04-27 Thread Paul Kinnucan
Hi John, I think you are on to something here. I failed to notice that Javier tried to launch a debuggee process twice in succession. Apparently JDE failed to get the message to connect to port 1900 on the first attempt, perhaps because standard I/O was blocked. On the second attemp, the message

RE: JDEBug vs Win2K and/or NT4: Status?

2001-04-27 Thread John L. Utz III
Wild guess made without looking at the code: it may be trying to connect twice because it somehow didnt get hooked up with the successful java connection to port 1900. so java has sucessfully engaged port 1900 and is patiently waiting there. JDEbug may have timed out and attempted to reconnect.

Re: JDEBug vs Win2K and/or NT4: Status?

2001-04-27 Thread Paul Kinnucan
r file, I'll give >it a spin and see what happens. > >- Original Message - >From: "Paul Kinnucan" <[EMAIL PROTECTED]> >To: "Javier Lopez" <[EMAIL PROTECTED]>; "Jim Goodwin" ><[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>

RE: JDEBug vs Win2K and/or NT4: Status?

2001-04-27 Thread Paul Kinnucan
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 -classic > > or something like > No response to command 2612. (process = 13; timeout = 30 s

Re: JDEBug vs Win2K and/or NT4: Status?

2001-04-27 Thread Martin Dickau
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 java

RE: JDEBug vs Win2K and/or NT4: Status?

2001-04-27 Thread Javier Lopez
Title: JDEBug vs Win2K and/or NT4: Status? 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 -classic   or something like No response to command 2612. (process = 13; timeout = 30 sec.)   But the