At 10:03 AM 12/17/99 -0800, Adam Ambrose wrote:
>I'm attempting to run jdebug on linux with the Sun/Inprise JDK, and am
>getting a different error from ones I've seen posted already posted to
>the jde list.
>
>
>Here's the Process Main(1) buffer output:
>
>*** Debugger Output for Process Main(1) ***
>
>Error: debugger unable to launch Main.
> Reason: VM initialization failed for:
>/usr/local/lib/javatools/jdk1.2.2_Sun_Inprise_RC1/jre/bin/java -Xdebug
>-Xnoagent -Djava.compiler=NONE
>-Xrunjdwp:transport=dt_socket,address=tigger.geoworks.com:2723,suspend=y
>-classpath
>/home/ambrose/jellyfish/tux-2/server:/home/ambrose/jellyfish/tux-2/lib
>Main /home/ambrose/jellyfish/tux-2
>Error: unable to run Main..
> Reason: Application ID '1' does not exist.
>
Hi Adam,
The debugger was unable to launch your application. (That is why you get
the "app id does not exist" message.) You can determine the reason why your
app did not launch by running
/usr/local/lib/javatools/jdk1.2.2_Sun_Inprise_RC1/jre/bin/java -Xdebug
-Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=tigger.geoworks.com:2723,suspend=y
-classpath
/home/ambrose/jellyfish/tux-2/server:/home/ambrose/jellyfish/tux-2/lib
Main /home/ambrose/jellyfish/tux-2
from a command shell. (If you want to know the meaning of all the arguments
in this command string, see the doc for jdb in the jdk1.2.2 tools
documentaion.) This is the same command line that jdebug uses to launch
your app (see error message). If you can't run this from a shell, jdebug
can't run your app.
Typically the reason jdebug is unable to launch an application is that you
forgot to include the jpda/bin directory in your system's command path.
- Paul
