At 03:46 PM 4/20/00 -0700, you wrote:
>
>Please enter the details of your bug report here
>
>Hi Paul,
>
>Thanks a lot for your timely response. It has been my pleasure to use
>JDE for developing my Java applications.
>
>I followed your advice and tried it again. I would like to report new
>observations:
>
>> >1. Clicking on 'Debug App' first time to start a debug session would
>> > cause a timeout error. The error message shown on the process
>> > buffer was:
>> >
>> > Error: debugger unable to launch gabriel.app.bib.impl.Bib.
>> > Reason: nil
>> >
>> > Note that I was able to run the application by clicking on 'Run
>> > App'.
>> >
>>
>> Increase jde-bug-debugger-command-timeout.
>
>I increased the time out to 360 seconds and still got the timeout.
>
>> >3. The output to stdout did not show on the CLI (2) buffer and the
>> > CLI (1) buffer disappeared.
>> >
>>
>> The CLI (1) buffer is still present, just buried. Look at the Emacs buffer
>> list.
>
>I checked the buffer list and did not find CLI(1).
>
>> The JDE creates a new set of buffers for each process that you start in a
>> debug session. You can remove all buffers for processes that have died in
>> the current session, using the JDEbug->Processes-Remove Dead Processes
command.
>>
>> Please in the future submit a problem report when asking for technical
support.
>
>I removed the dead provesses using the suggested command and started a
>debug session thereafter. I found that the debug history is now in
>Process (2) buffer and I could see CLI (2) showing stdout of the
>program execution.
>
>I did find an error reported from the debugger while starting the
>session. The error said (sort of):
>
> Process id 1 not found ..
>
Hi Shih-Ming,
I was able to reproduce this error on:
Emacs : GNU Emacs 20.3.1 (sparc-sun-solaris2.5, X toolkit)
Package: JDE version 2.1.6beta23
(essentially the same configuration as yours). The debugger fails to
respond to the first launch command within the timeout period but responds
to subsequent launch commands. The problem seems to be in the code that
sets up a socket for displaying the CLI output in the Emacs buffer. I'll
investigate. Meanwhile, I suggest as a workaround that you try starting the
debugger first via JDEbug->Processes->Start Debugger. This works for me.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
