Tom Reilly wrote:
Hi Tom,
I have exactly the same problem. I reported the issues. A few people claimed
that they got it working (one of them when we entered in details admitted that he
actually did not use it
probably just got it running as you and I did) others said that they were able to
step through using JDebug.
Unfortunately nobody was willing to give their settings so I suspect that
actually nobody really used JDEbug on Linux
or at least I have no proof. It woulfd be nice to see the buffer with the debugger
commands from one of those who
succeded using JDEbug on Linux.
You can see what commands are used looking at the debugger output buffer. I cannot
recall right now its name,
but you can find it looking at the buffer list from menu or C-x C-b gives you the
list.
Bogdan
> 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?
>
> Thanks in advance,
>
> --
> Tom Reilly
> Allaire Corp.
> http://www.allaire.com
