----- 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/or NT4: Status?
> hi John,
>
> I don't know if hard coding the number is the best solution.
> I was looking at this problem last week, let me tell you what I found.
> I tried starting the JDEBug process outside the JDE and I still got the
same
> problem. The problem in question is that the process for some mysterious
> reason is not showing all the output that the debugger is sending. If you
> send and EOF signal in the buffer that contains the process
> the missing output shows up but the EOF kills the
> process. The next thing I was going to do was to check if the java
> code was flushing all the output that was sending to the process.
>
I agree with Javier. I believe the problem is that JDEbug is able to start
the socket but is unable to to report the port number back to Emacs/JDE,
either because the thread that creates the socket (and reports the port
number) is blocked or because JDEbug's standard out buffer is not being
flushed for some reason.
- Paul
