At 10:47 AM 10/30/00 +0200, Gert van Rooyen wrote:
>Hello,
>
>I am unable to solve the following problem:
>
>Having just installed: JDE2.2.6 beta 3, semantic-1.3.1, speedbar-0.13a,
>elib-1.0,
>JDK1.3 (re-installed).
>
>Compiling and running a test program works fine.
>
>Debug does not work: After toggling a breakpoint I try: JDE -> Debug App.
>Next thing is a message from the Java Virtual Machine Launcher: "Could not
>initialize the Java
>Virtual Machine. Program will exit."
>
>(I have seen a similar query for a Linux environment, but what to do on
>Windows?)
>
>Below is the full problem report with .emacs included.
>
[snip]
>The contents of the *JDEBug* buffer were
>
>cd c:/tmp/
>javaw -classpath
>d:/Gnu_stuff/Emacs/emacs-20.5/site-lisp/jde-2.2.6beta3/java/lib/jde.jar;d:/j
>dk1.3/lib/tools.jar jde.debugger.Main
>
>
>(jde-dbo-init-debug-session)
>
>JDE> -1 1 launch 1 -vmexec javaw -classic -classpath . -v -verbosegc Test2
>
>
>(jde-dbo-message 1 "VM options: '-classic '")
>
>
>(jde-dbo-command-error
>1 "VM initialization failed for:
>D:/JDK1.3/bin/javaw -classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdw
>p:transport=dt_shmem,address=javadebug,suspend=y -classpath . -v -verbosegc
>Test2")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is the command line that JDEbug uses to launch Test2. One way to diagnose
launch failures is for you to use the same command line in a shell to try to
launch the application. Often this will enable you to get diagnostic messages
that JPDA suppresses. So, execsute M-x shell and enter
D:/JDK1.3/bin/javaw -classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdw
p:transport=dt_shmem,address=javadebug,suspend=y -classpath . -v -verbosegc
Test2"
at the shell prompt. If you are unable to launch the application this way,
neither will JDEbug. On the other hand, if you are able to launch the app,
let me know and I will investigate further.
- Paul
