At 09:43 AM 2/27/00 +0200, you wrote:
>>>>
thanx. i can't launch the debugger. if you're not the person to contact, or this isn't the way to contact you, please tell me how. here is the case description: i have xemacs 21.1.6 on windows nt. we're working with symantec's java vm. jdk 1.2.2 i've unzipped jde under ~/emacs/jde (and changed load-path to point to it) . and copied the java sub directory under xemacs-packages/etc/jde/java i've downloaded jpda. i've unzipped it to
<<<<
This won't work as the JDE assumes that the java directory is relative to the lisp directory. If you simply delete or rename the existing XEmacs jde data directory and point your load-path to the lisp subdirectory of the JDE distribution, everything will work fine.

For what it's worth, I don't recommend using the JDE with the native Windows version of XEmacs as there are some incompatibilities. In particular XEmacs does not handle creation of subprocess windows correctly. Java developers are better off using GNU Emacs under Windows. (Unix XEmacs and perhaps Cygnus XEmacs seem to be okay.)
>>>>
d:/programs/jdpa i've setup the customization variables to point to jdk and jdpa, use java (not javaw). when i try to launch the debugger i get a 'couldn't start the debugger' message. i debugged the functions somewhat and the problem is for 2 reasons: a. the classpath isn't setup right. when i changed it to include also $classpath and added the
<<<<
Interesting. I didn't think this was feasible. The JDE uses XEmacs subprocess launch function to launch the JDE so it's puzzling to me that including an environment variable would work. I wonder who is doing the environment variable expansion. Emacs? the VM? The fact that you are using Unix syntax would seem to indicate that it is the XEmacs subprocess command that is doing the variable expansion as the vm is a Windows program and thus would not be expected to understand Unix environment variables.

Anyway, if the JDE is installed the way it is intended to be installed fiddling with the classpath in this way would not be necessary.

>>>>
pointers to jde.jar there, it works. b. the jde-jbs-choose-vm chooses javaw although i specifically chose java. when i changed the function to always return java, it works. hope this
<<<<
Again, not necessary. On Windows, this function uses the value of the jde-run-java-vm-w, on Unix, jde-run-java-vm. (If you are using the Cygnus version of XEmacs, of course, the JDE thinks it is running on Unix. Life would be much simpler if the XEmacs schism had never taken place.

Please note that JDEbug is still in beta and I have not made any effort to ensure compatibility with XEmacs beyond implementing fixes occasionally sent to me by XEmacs users. So expect to lots of rough edges and bugs.

- Paul

------------------------------------------------------------------------------
JDE website: http:/sunsite.auc.dk/jde/

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.

Reply via email to