At 09:17 PM 6/28/00 +1200, you wrote:
>I've got the latest version of JDE , 2.1.7
>I've got the JDK 1.3 from sun.
>I've got windows emacs 20.6.1.
>
>I've set up everything as specified on the JDE website.
>
>It all works fine (compilation, running), except for one thing.
>I can't get the debugger JDEbugger to work at all.
>
>I do a JDEbug>Process>Start debugger (from the source buffer)
>I get a message debugger started successfully.
>
>I do a JDEbug>Process>Launch Process
>I get the message:
>*** Debugger Output for Process Ex19(2) ***
>
>Debugger waiting for Emacs to connect to app SIO port 1068.
>vm started...
>All threads suspended...
>Emacs connected to standard IO port 1068 for process Ex19.
>VM options: '-classic '
>Launched VM Java Debug Interface (Reference Implementation) version 1.3
>Java Debug Wire Protocol (Reference Implementation) version 1.0
>JVM Debug Interface version 1.0
>JVM version 1.3.0 (Classic VM, native threads, nojit)
>
>According to the documentation, I should now be stopped on the first line
>of the program, and should be able to able to Step Over, Step Into, etc.
>But I can't. Those options are greyed out.
>
The wording in the manual is misleading (and has been corrected in the
upcoming release). The launch command launches the application process,
which halts BEFORE invoking the application's main method. At this point,
there are only two things you can do: set breakpoints and issue a Continue
command. So the solution is to set a breakpoint (or breakpoints) and then
issue a Continue command. This will cause the application to run to the
initial breakpoint at which point you can start stepping, etc.
This is a FAQ, BTW. Perhaps somebody could update the FAQ-o-matic FAQ on
the website.
- Paul
