At 10:45 AM 2/25/00 -0500, you wrote:
>Hi,
>
>I'm trying to use the JDEbug form 2.16beta20, on a NTEmacs 20.4.1, using
>bash as the shell. I'm not having much success, though...
>
>I set a breakpoint in the beginning of main() in my application, and
>them use C-c C-v C-d to start the debugger (at that point, the step
>commands in the JDEbug menu are disabled, which I think is strange). The
The JDE enables the step menus only when a process exists and is suspended
by the debugger. Why do you find this strange?
>windows is partioned in three areas as it should, but then I got the
>following messages in the bottom area:
>
>vm started...
>All threads suspended...
>Launched VM Java Debug Interface (Reference Implementation) version 1.0
>Java Debug Wire Protocol (Reference Implementation) version 1.0
>JVM Debug Interface version 1.0
>JVM version 1.2.2 (Classic VM, build JDK-1.2.2-W, native threads, nojit)
>
>Launching vm to run AvatarFactory
>Setting breakpoint at line 8 in AvatarFactory.java.
>Setting breakpoint at line 22 in AvatarFactory.java.
>Setting breakpoint at line 52 in AvtSnmpDriver.java.
>Running AvatarFactory.
>AvatarFactory process ended.
>Application I/O closed
>Application I/O closed
>Input error; application I/O closed
This is a spurious message that I have not gotten around to surpressing.
>vm disconnected...
>
>I never have a chance to stop in a breakpoint. And it is similar with
>other applications as well; they end very quickly, and never stop at the
>first breakpoint. Any ideas? It seems to be related to some I/O problem.
Yes, but I need more info. Please submit a full problem report.
>The applications are server-style, with on GUIs or keyboard input
>
>Another strange behavior is that the buffers created by JDEbug (like
>"Process <APP_NAME>(<number>)" ) are never deleted, even when I call
>"Exit Debugger" from the menu. Every time I try to run the debugger a
>new set of buffers is created.
>
The JDE does not delete buffers automatically when a process dies for two
reasons:
1) Messages relating to process status arrive asynchronously and a
message that was sent before the process died may appear after notification
that it died.
2) You might want to keep the buffers of a dead process around for
post-mortem analysis.
To remove all traces of dead processes from the current session, including
buffers, use the JDEbug->Processes->Remove Dead Processes command.
- Paul
------------------------------------------------------------------------------
JDE website: http:/sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
If you have a problem with the JDE, please use JDE->Help->Submit Problem
Report to prepare your query. This will insure that you include all
information that may be required to solve your problem.
