I get the following error when launching a process using JDEbug.  When I don't use the 
"classic" mode, I don't get an explicit error message, but it doesn't seem to work 
(the buffer is included at bottom).  I assume that this is the bug in HotSpot mode.  
When I do use the "classic" mode, I get "Error: debugger unable to launch App."  When 
I run the command (with "classic" mode) in a shell, I get :"Error: no `classic' JVM at 
`C:\Program Files\JavaSoft\JRE\1.3.0_01\bin\classic\jvm.dll'."

If this is the same JDEbug initialization error that has been posted several times, 
I'm sorry and please let me know.

thanks in advance
Max

Output when trying to debug with "classic" mode:

*** Debugger Output for Process App(5) ***

Launch command line:
  javaw -classic -classpath 
.;c:\\jdk1.3.0_01\\jre\\lib\\jakarta-oro-2.0.2-dev-2.jar;c:\\AppDevStudio\\Java\\Misc\\webAFServerPages.jar;c:\\AppDevStudio\\Java\\SAS\\ext\\remoteobj.jar;c:\\AppDevStudio\\Java\\SAS\\ext\\netutil.jar;c:\\AppdevStudio\\Java\\SAS\\ext\\connect.jar;c:\\AppdevStudio\\Java\\SAS\\ext\\webAF.jar;c:\\jdk1.3.0_01\\lib;c:\\itsv3\\Web-inf\\classes;c:\\jdk1.3.0_01\\jre\\lib
  App  

Error: debugger unable to launch App.
  Reason: VM initialization failed for: C:/Program 
Files/JavaSoft/JRE/1.3.0_01/bin/javaw -classic -Xdebug -Xnoagent -Djava.compiler=NONE 
-Xrunjdwp:transport=dt_shmem,address=javadebug,suspend=y -classpath 
.;c://jdk1.3.0_01//jre//lib//jakarta-oro-2.0.2-dev-2.jar;c://AppDevStudio//Java//Misc//webAFServerPages.jar;c://AppDevStudio//Java//SAS//ext//remoteobj.jar;c://AppDevStudio//Java//SAS//ext//netutil.jar;c://AppdevStudio//Java//SAS//ext//connect.jar;c://AppdevStudio//Java//SAS//ext//webAF.jar;c://jdk1.3.0_01//lib;c://itsv3//Web-inf//classes;c://jdk1.3.0_01//jre//lib
 App
VM options: '-classic '


Output when trying to debug without "classic" mode:

*** Debugger Output for Process App(4) ***

vm started...
All threads suspended...
Launch command line:
  javaw -classpath 
.;c:\\jdk1.3.0_01\\jre\\lib\\jakarta-oro-2.0.2-dev-2.jar;c:\\AppDevStudio\\Java\\Misc\\webAFServerPages.jar;c:\\AppDevStudio\\Java\\SAS\\ext\\remoteobj.jar;c:\\AppDevStudio\\Java\\SAS\\ext\\netutil.jar;c:\\AppdevStudio\\Java\\SAS\\ext\\connect.jar;c:\\AppdevStudio\\Java\\SAS\\ext\\webAF.jar;c:\\jdk1.3.0_01\\lib;c:\\itsv3\\Web-inf\\classes;c:\\jdk1.3.0_01\\jre\\lib
  App  

Emacs connected to standard IO port 4436 for process App.
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.0_01 (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 4436.
Debugger connected to standard I/O socket.
Error: cannot evaluate "System.out.println(i)".
 Reason: Invalid frame.
Error: cannot evaluate "i".
 Reason: Invalid frame.

Reply via email to