At 08:08 AM 1/7/00 +1000, Steve Carter wrote:
>Hi there,
> I am using JDE 2.1.5, emacs 20.3.1, JDK 1.2.2 on NT4.
>
>QUESTION 1.
>----------------
>While I generally have no trouble setting breakpoints when debugging Java
>code, sometimes I get a message similar to the following that prevents
>setting breakpoints.
>
>No code at line 1374, or class is optimized.
>
This usually happens when you try to set a breakpoint in an inner class or
anonymous class. The current Java debug architecture does not support this.
JDK 1.3 has a new debug architecture, JPDA, that permits setting
breakpoints anywhere. You can retrofit JPDA to JDK 1.2 by installing and
downloading the JPDA add-on package for JDK 1.2 from Sun's website. If you
want to use JPDA with the JDE, you have to download the latest beta version
of the JDE and use its JPDA-based debugger, JDEbug.
>
>
>QUESTION 2.
>----------------
>The Up stack (C-x C-a <) and Down stack (C-x C-a >) commands in JDE work
>fine with the exception that the source file matching the stack frame
>pointer is not displayed automatically. I have to manually find the file and
>goto the line of interest to examine the source code. This is a bit of a
>frustration.
>
I never got around to providing a JDE interface to jdb's stack commands.
The current version of JDEbug also does not (yet) provide stack frame
navigation and source tracking. My plan is to add this feature soon.
- Paul
