At 06:47 PM 4/25/00 -0400, you wrote:
>Well, now that I can debug a GUI, it seems that when trying to debug a
>console application, the debugger won't stop at the breakpoint. In a
>test app, I set the breakpoint on the main declaration, then ran C-c C-v
>C-d, and this was my output:
>
>*** Debugger Output for Process URShift(1) ***
>
>Debugger waiting for Emacs to connect to app SIO port 1438.
>vm started...
>All threads suspended...
>Launched VM Java Debug Interface (Reference Implementation) version 1.0
>Java Debug Wire Protocol (Reference Implementation) version 1.0
>JVM Debug Interface version 1.0
>JVM version 1.2.2 (Classic VM, build JDK-1.2.2-001, native threads,
>nojit)
>Debugger created socket for app I/O on local host at port 1438.
>Emacs connected to standard IO port 1438 for process URShift.
>Setting breakpoint at line 24 in URShift.java.
>Running URShift.
>Input error; application I/O closed
>Application I/O closed
>Application I/O closed
>URShift process ended.
>vm disconnected...
>
>Any ideas?
>
The breakpoint is not on the execution path of the app or the app was
compiled with jikes.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
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
