At 01:45 PM 4/20/00 -0700, you wrote:
>
>Hi,
>
>I just installed jde-2.1.6beta23 with Solaris 2.5.1 and FSF Emacs
>20.3.1. While using JDEBug to debug my program, I observed the
>following behaviors:
>
>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.
>2. Clicking on 'Debug App' the second time somehow started the debug
> session but the local variables somehow got shown on the Local
> Variable (1) instead of the second one. Also, only the process 1
> buffer had the debug session history.
>
> Note that I could step over statements and examine variable values.
>
It's possible the timeout error confused the debugger.
>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.
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.
- 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
