Hello Debuggers,
I would like to use the debugger to (try to) analyse what happens inside
some JDK-source class (e.g. java.io.ObjectInputStream). I included the path
to the JDK sources in the jde-db-source-directories variable. (BTW, I had
to put the JDK source path on the first line, and the local source
directory "." on the second line. The other way round it prompted for the
JDK source path, providing only the local source path.) I set some
breakpoint and put a trace on method entries. When I run "Debug App" it
stops at the breakpoint. When I do "Step Into" a method list appears in the
debugger window (together with some error messages on max-lisp-eval...??).
Fine, but:
Is there a way I could do a *single* step into a method, get the (current,
relevant) source code displayed (with the ==> pointer) and then
step..step..step through the method while I get the chance to investigate
how variables change?
(Emacs 20.5.1, Win95, JDK 1.3beta, jde2.1.6beta15. Could not get the deb
ugger to work with jdk1.2. My jpda1_0-win distribution did not include the
jpda.jar file anywhere (only jbug.jar), which the debugger wanted)
Relevant part of .emacs file:
(custom-set-variables
'(jde-bug-jdk-directory "d:/jdk1.3/")
'(mark-even-if-inactive t)
'(jde-db-source-directories (quote ("d:/jdk1.3/src/classes/" ".")))
'(jde-compiler "javac")
'(jde-jdk-doc-url "D:/jdk1.2/docs/api/index.html")
'(jde-db-debugger (quote ("jdebug" . "Class")))
'(jde-run-working-directory "")
'(jde-global-classpath (quote ("." "d:/jdk1.3/jre/lib/rt.jar")))
'(jde-bug-jpda-directory "")
'(jde-bug-vm-includes-jpda-p t)
'(jde-db-option-verbose (quote (t t nil)))
Thank you,
Gert.
