-----Original Message-----
From: Richard den Adel <[EMAIL PROTECTED]>
To: Caryn <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, December 05, 2000 1:18 AM
Subject: Re: Problems with compilation of the debugger source
Application.java in both 2.2.5 and 2.2.6 beta7
>Caryn wrote:
>
>>
>> A lot of people have had this problem, mainly on Windows. Unfortunately I
>> have never been able to reproduce it on any of my Windows or Solaris
>> systems. It seems to occur when Emacs tries to connect to a socket
created
>> by JDEbug to connect the standard I/O of the application to Emacs. The
>> socket connection never gets made. Some people have found that removing
all
>> versions of the JDK and reinstalling a single version clears up the
problem.
>> I suspect the problem may be a thread deadlock somewhere. The JDEbug Java
>> code is heavily threaded. However, I didn't write the code and I haven't
had
>> time to try to analyze it to see where deadlocks might occur. I put in
some
>> messages designed to instrument each stage in the standard I/O socket
>> creation and connection process. It is my hope that somebody, hopefully a
>> multithreading expert, who has this problem will take a cue from this and
>> try to pinpoint exactly where the hangup occurs.
>>
>> - Paul
>>
>
>Not that I am a great multithreading expert, but I want to take a look
>at the sources and what is going wrong. The compilation errors in
>Application.java prevent me from doing that. Is the source tree exactly
>the same as the one you build your jar with? If not, could you please
>sent me a copy of the correct source tree.
>
Yes, the source tree is exactly the same. I don't know why you got
compilation errors. I don't get them when building the distribution, using
the JDk 1.3 javac. (Note: I am at the XML 2000 conference where I don't have
access to the machine I use for JDE development so I can't be of much help
until I return on Wed. evening.)
- Paul
