At 01:55 PM 2/28/00 +0000, you wrote: > > Hi, > > I'm using the Cygwin bash shell with my Emacs and I can't invoke JDEbug to > debug my application, instead I get the following: > > Error: debugger failed to start. > > Just to ascertain if the problem was with the sem-colons I altered jde-dbs.el > so that the classpath path was wrapped with double-quotes for the above line. > This did not help, and confirmed you assessment that the semi-colons were not > the problem. > > I originally sent this problem to the newsgroup, where you informed me to use > the submit problem report feature of the JDE. [snip] > > > The contents of the *JDEBug* buffer were > > javaw -classpath > c:/usr/reazul/lisp/jde-2.1.6beta20/java/src;c:/usr/reazul/lisp/jde- ^^^^^ This is why I hate the Windows version of XEmacs. It does not launch subprocesses correctly. With this version, if you use javaw to launch the vm that runs the debugger you don't get the debugger's standard out so the JDE thinks the debugger was never launched. You need to change jde-run-java-vm-w from javaw to java. The problem now is that if you are debugging a GUI app, you're probably going to see an extraneous DOS window when the app is launched. NT/Emacs does not have this problem because the NT/Emacs got subprocess launching correct (after many attempts)--something that still eludes the NT/XEmacs team. I wish the NT/XEmacs team would take the time to figure out how NT/Emacs launches subprocesses and copy what they did. - Paul > > 2.1.6beta20/java/lib/jde.jar;c:\jpda1_0-win\lib\jpda.jar jde.debugger.Main > > > > > End Insert *JDEbug* buffer > [snip] ------------------------------------------------------------ JDE mailing list archive: http://www.mail-archive.com/[email protected]/maillist.html If you have a problem with the JDE, please use JDE->Help->Submit Problem Report to prepare your query. This will insure that you include all information that may be required to solve your problem.
