Now I upgraded to jdk 1.3.1 RC-1 and my test case works with xemacs.
The release notes for jdk 1.3.1 say that there were problems with
the JPDA in 1.3 + hotspot, and I know that Optimizeit didn't work with
hotspot VMs before 1.3.1, so perhaps JDEbug is a victim of the same bugs?
At any rate, I can now debug in both emacsen. Hooray for me! <smile>
Xemacs has the same problem as FSF emacs when it comes to watching
for access: the debugger doesn't understand a command argument `-sp.'
Eric
In message <[EMAIL PROTECTED]>, eric writes:
:
: In message <[EMAIL PROTECTED]>, "Eric D. Friedman"
> w
: rites:
: :
: : Using FSF emacs (will try xemacs shortly) and 2.2.7b10, I was able to
: : debug the test code I wote about earlier.
:
: OK, I tried xemacs and it does *not* work. Using top, sorted by
: CPU usage, I see several java processes (which represent threads on
: linux), all of which are inactive. Is it possible there's a thread
: synchronization issue?
:
: I'm doing this in a `vanilla' setup. That is,
: `xemacs -q -l just-enough-lisp-to-load-jde-beta.el path/to/my/test/Main.java'
:
: Eric
:
