At 10:45 AM 8/10/00 +0200, you wrote:
>Didn't help to define jde-global-classpath.
>
>The run that you got now is the result of starting emacs, running the
>program using ^c^v^r and then tryin g^c^v^d
>
>The contents of the *JDEBug* buffer were
>
>cd c:/data/java/
>javaw -classpath
>c:/data/emacs/site/jde-2.2.1/java/lib/jde.jar;c:/jdk1.3/lib/tools.jar
>jde.debugger.Main
>
>
>(jde-dbo-init-debug-session)
>
>JDE> -1 1 launch 1 -vmexec javaw -classic -classpath
>C:\data\java\classpath\jakarta-regexp-1.1.jar;c:\data\java;C:\data\java\clas
>spath\jswat.jar;c:\jdk1.3\lib\tools.jar;c:\data\classpath\activation.jar;c:\
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
These are not necessary and may be causing problems, especially jswat.jar.

That is why I asked you to include only the paths you absolutely need to
run your application.

Most problems with JDEbug on Windows are the result of intallation of
multiple tools, i.e., multiple JDKs, multiple debuggers, IDEs. In such
messy environments, one is never sure if the right versions of classes are
being loaded.

- Paul

Reply via email to