Hi Paul,

Thanks for the info, the debugger is working fine now. But I would
appreciate if you could modify the next version of jde to be able to specify
the full path to a jvm. I always use the full path since it allows me to
test my code with severals vm. In the mean time I have set my path to point
to the default vm.

Thanks again and keep-up the good work, jde is really cool.

----------------------------------
/*
 * Jean-Pierre Dub�
 * Infocom enr.
 * Developpement de logiciels
 * Software development
 *
 */



----- Original Message -----
From: "Paul Kinnucan" <[EMAIL PROTECTED]>
To: "Jean-Pierre Dub�" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, December 01, 1999 10:33
Subject: Re: The debugger doesn't want to start


At 09:49 AM 12/1/99 -0500, Jean-Pierre Dub� wrote:
>
> Hi,
>
> I downloaded the latest beta 2.1.16 and installed it on my system,
> Windows-2000 with NT/Emacs 20.4.1. I have set all the appropriate
parameters
> as mention in the readme that come with jde. I also installed JPDA and
added
> the ...\jpda\bin to my path. I see the JDEbug menu and I can set
breakpoints
> in my code. But when I start the debugger I get the following error
message
> in the JDEbug buffer:
>
> c:/devtools/jdk1.2/bin/javaw -classpath
>
c:/bin/emacs-20.4/lisp/jde-2.1/java/lib/jde.jar;/devtools/jpda/lib/jpda.jar
> jde.debugger.Main
>
>
> (jde-dbo-init-debug-session)
>
> JDE> -1 1 launch 1 -use_executable c:/devtools/jdk1.2/bin/javaw -classpath
> /softdev/hq/hq1817/classes;/softdev/java/library/classes/infocom_lib.jar
> autoeval.Main
>
>
>
> (jde-dbo-debug "                             |----------- PROBLEM SHOULD
BE
> HERE -----------------|
> java.io.IOException: CreateProcess:
> c:\devtools\jdk1.2\jre\bin\c:/devtools/jdk1.2/bin/javaw -Xdebug -Xnoagent
> -Djava.compiler=NONE -Xrunjdwp:transport=dt_shmem,address=javadebug,suspen
d=y
> -classpath
> /softdev/hq/hq1817/classes;/softdev/java/library/classes/infocom_lib.jar
> autoeval.Main  error=123
>  at java.lang.Win32Process.create(Native Method)
>  at java.lang.Win32Process.<init>(Win32Process.java:64)
>  at java.lang.Runtime.execInternal(Native Method)
>  at java.lang.Runtime.exec(Runtime.java:272)
>  at java.lang.Runtime.exec(Runtime.java:219)
>  at
> com.sun.tools.jdi.AbstractLauncher$Helper.launchAndAccept(AbstractLauncher
> .java:147)
>  at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:100)
>  at
> com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.jav
> a:144)
>  at jde.debugger.Application.launch(Application.java, Compiled Code)
>  at jde.debugger.Application.initialize(Application.java:163)
>  at jde.debugger.Jdebug.initApplication(Jdebug.java:403)
>  at jde.debugger.Jdebug.doLaunch(Jdebug.java:437)
>  at jde.debugger.Jdebug.handleGeneralCommand(Jdebug.java:278)
>  at jde.debugger.Jdebug.access$0(Jdebug.java:260)
>  at jde.debugger.Jdebug$1.run(Jdebug.java:210)
> ")
>
>
> (jde-dbo-command-error
> 1 "Unable to launch: java.io.IOException: CreateProcess:
> c:\devtools\jdk1.2\jre\bin\c:/devtools/jdk1.2/bin/javaw -Xdebug -Xnoagent
> -Djava.compiler=NONE -Xrunjdwp:transport=dt_shmem,address=javadebug,suspen
d=y
> -classpath
> /softdev/hq/hq1817/classes;/softdev/java/library/classes/infocom_lib.jar
> autoeval.Main  error=123")
>
> The problem should be where jde try to start the app and issue the
following
> command: " c:\devtools\jdk1.2\jre\bin\c:/devtools/jdk1.2/bin/javaw" this
is
> not right?
>
> Any help would be appreciated. My .emacs file can be found as an
attachment
>



There is obviously a problem somewhere with specifying the command to start
the
debuggee vm. It appears that either JDEbug or JPDA does not want a fully
qualified path name. I will look into this. In the meantime, you should try
just specifying javaw in jde-run-java-vm-w.

- Paul

>
> Thanks.
>
>
> ----------------------------------
> /*
>  * Jean-Pierre Dub�
>  * Infocom enr.
>  * Developpement de logiciels
>  * Software development
>  *
>  */
>
> Content-type: application/octet-stream; name=.emacs
> Content-disposition: attachment; filename=.emacs



Reply via email to