At 03:36 PM 3/22/00 -0500, you wrote:
>Hello all,
>
>Does anyone know what conditions need to be satisfied for JDb menu to appear
>when in the .java buffer? It seems to be inconsistent. I'm using JDE
>2.1.6beta10 (and also 2.1.4) with NTEmacs 20.6.1 (although it did the same
>thing with older versions of both). The JDb menu has some important
>selections (setting and clearing breakpoints, printing expressions, etc),
>but it seems to show up when it wants to. I could use the shortcuts defined
>on the menu (for example 'M-x space' to set a breakpoint) even though the
>menu doesn't seem to show, so I know the conditions for displaying the menu
>should be met (i.e., I'm in a java frame while running the debugger).
>
The JDE provides a "source-level" debugging front-end to jdb, which is a
command-line debugger. The front-end is based on gud, Emacs' generalized
front-end to command-line debuggers. When I first created the JDE, I did
the minimal changes needed to get gud to support jdb (it did not support
jdb at the time.) So the functionality you are seeing is essentially gud.
The gud-based front-end works by issuing commands to jdb via a pipe and
parsing the output messages that come back from jdb. The front-end is
interested in two types of messages: breakpoint hit and step taken. These
messages indicate the name of the class and the line number where a
breakpoint was hit or where the next step was taken. The front-end extracts
the class and line number from the message using regular expressions and
then uses this information plus the list of source directories in
jde-db-source-directories to look for the corresponding source file. If the
front-end finds the source file, it opens the source file in a jde-mode
buffer and installs the Jdb menu in it. So you see, you get the Jdb menu
only in source buffers that have been visited as the result of a breakpoint
being hit or a step being taken.
>Also, I do remote debugging to debug servlets and jsps. Does anyone know
>what settings I need to set to prevent the "run com.company.objectname.main"
>from executing once the debugger starts? I use the "jde-db-read-vm-args" to
>enter the password for connecting to a remote vm but it still tries to
>execute the run command after connecting.
>
The JDE->Debug App is a convenience command that does the most common
things most people want to do at the start of a debug session, namely,
start the app in debug mode, set an initial breakpoint, and run to that
breakpoint. The Debug App sets the initial breakpoint at the beginning of
your apps main method and runs the app. If you'd like to just launch or
connect and stop, enter M-x customize-variable
jde-db-set-initial-breakpoint and set the variable off.
- Paul
------------------------------------------------------------
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
Please use JDE->Help->Submit Problem Report when reporting a bug or seeking
help. This will insure that you include all information that may be
required to solve your problem.
