Tom Reilly writes:
>
> I'm trying to get JDEBug to work on my Linux box with Blackdown's RC4.
> I think I got everything set up right but when I try to launch the
> debugger I get this:
>
> *** Debugger Output for Process JRun(2) ***
>
> 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.2.2 (Classic VM, build Linux_JDK_1.2.2_RC4, native threads, nojit)
> Launching vm to run JRun
> Running JRun.
> vm started...
> All threads suspended...
> JRun process ended.
> vm disconnected...
>
>
> It looks like my program is dying but no ouput shows up in the Local
> Variables buffer and it doesn't show me the exact command line its
> using to launch it so I'm kinda stuck. Is there some switch I can
> toggle to get jdebug to show me the command line its using to launch
> the Java process?
Look in the *JDEbug* buffer. It doesn't show you the exact command
but you can piece together what is going on from the content.
IMHO, JDE needs a lot more testing on Linux. I wonder if Paul K has a
test suite we can use to verify that a JVM port handles JPDA and
JDEBug sufficiently rather than using lots of different applications
to ferret out the bugs. If not then I'll gladly collect submittals
and use them to build and contribute a test suite.
My experience is that JDEbug works on the HelloWorld program but will
not work on my DB Editor application. Trying to nail down the errant
code is a royal pain in the butt. Also, I'm somewhat suspicious of
jikes generated code. I strongly suggest we use javac until JDEbug on
Linux is known to be rock solid.
> Thanks in advance,
No problem,
Dad
