Hi Paul,
I tried the high-level approach and the low-level approach, using the
sequence of operations you outlined, to no avail.
Here's the debug process output from the high-level output. Note
that the breakpoint is being set by JDE->Debug App and that the app still
does not stop at this breakpoint.
*** Debugger Output for Process FooBar(1) ***
Launch command line:
java -classpath
/home/eric/classes/xerces.jar:/home/eric/prj/ETJavaFoundation/classes:/home/eric
FooBar
Emacs connected to standard IO port 33841 for process FooBar.
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.1-beta (Java HotSpot(TM) Client VM, interpreted mode)
vm started...
All threads suspended...
initSIOConnect: starting standard I/O handshake.
initSIOConnect: starting SIO connect thread.
Debugger waiting for Emacs to connect to app SIO port 33841.
Setting breakpoint at line 21 in FooBar.java.
Debugger connected to standard I/O socket.
Running FooBar.
FooBar process ended.
Closed transport for application's standard output.
Closed transport for application's standard error output.
In message <[EMAIL PROTECTED]>, Paul Kinnucan write
s:
: Eric,
:
: The behavior you report is consistent with a properly working JDEbug not
: being used correctly. Please refer to the section on launching applications
: in the JDEbug user guide. Note that if you use JDEbug->Processes->Launch,
: you must set breakpoints AFTER executing JDEbug->Processes->Launch and
: BEFORE executing JDEbug->Continue. Any breakpoint set before executing
: JDEbug->Processes Launch will have no effect.
:
: As the JDEbug user guide explains, there are two ways to launch an
: application: one is a high-level way that does all the stuff required to
: launch and run an app to an initial breakpoint; the other is a low-level
: way that requires that you do everything yourself in the right order.
: You've chosen the low-level way. If you want to use this approach, you
: should read the JDEbug user's guide carefully to understand what is going
: on. If the guide is not clear, let me know so that I can improve it.
:
: - Paul
:
: At 12:17 PM 2/26/01 -0800, Eric D. Friedman wrote:
: >
: >Is anyone able to use JDEbug on solaris/xemacs? This is with
: >jde 2.2.6.2
: >
: >I've followed the instructions for setting up JDEbug and am using
: >the 1.3.1 beta VM, which is supposed to have fixed the problems with
: >debugging in hotspot VMs (solaris does not have a "classic" vm).
: >
: >I coded up a simple class that has a main method that creates a single
: >instance and invokes a single member method:
: >
: >String foo(String foo) {
: > foo += "y"; // breakpoint set here
: > foo += "z";
: > return foo;
: >}
: >
: >I start up the debugger and do a JDEbug->Processes->Launch Process.
: >The app starts, but there's no indication that my breakpoint has been
: >hit (nothing shows up in the Locals buffer, though `foo' is definitely
: >a local with a value at this point.
: >
: >JDEbug->Continue runs the app to completion without hitting my breakpoint.
: >If I set two breakpoints, the same thing happens, so I'm pretty sure
: >that it's not a problem of the display not being updated to the breakpoint.
: >
: >The debugger output follows.
: >
: >Thanks,
: >Eric
: >
: >*** Debugger Output for Process FooBar(5) ***
: >
: >vm started...
: >All threads suspended...
: >Launch command line:
: > java -classpath
: >/home/eric/classes/xerces.jar:/home/eric/prj/ETJavaFoundation/classes:/home/
: >eric FooBar
: >
: >Emacs connected to standard IO port 33819 for process FooBar.
: >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.1-beta (Java HotSpot(TM) Client VM, interpreted mode)
: >initSIOConnect: starting standard I/O handshake.
: >initSIOConnect: starting SIO connect thread.
: >Debugger waiting for Emacs to connect to app SIO port 33819.
: >Debugger connected to standard I/O socket.
: >Running FooBar.
: >FooBar process ended.
: >vm disconnected...
:
