At 06:19 PM 1/4/00 +0100, Gert van Rooyen wrote:
>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...??).
This sounds like a bug to me. It would help if you used repeated the exact
steps
that caused this and then execute the JDE->Help->Submit Bug Report to
capture the
state of the JDE. Then mail the bug report to me.
In any case, you might want to check the path to the JDK 1.3 source files.
See below.
co
>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?
>
Yes. This works perfectly on my system.
>(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)
>
I'll look into this.
>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/" ".")))
^^^^^^^^^^^^^^^^^^^^^^
On my system, this is
.../jdk1.3/src/share/classes/
^^^^^
- Paul
