Bryan Ischo <[EMAIL PROTECTED]> writes:
[snip]
> To make a long story short, jde-db creates a running instance
> of jdb which simply hangs. This is what I get:
>
> ------------------------------------------------------------------------
> cd /data/den/bji/com/plumbdesign/pdanvil/gui/
> jdb com.plumbdesign.pdanvil.gui.PDAnvil
>
> Initializing jdb...
> > Deferring breakpoint com.plumbdesign.pdanvil.gui.PDAnvil.main.
> It will be set after the class is loaded.
> > run com.plumbdesign.pdanvil.gui.PDAnvil
> >
> VM Started: Set deferred breakpoint request com.plumbdesign.pdanvil.gui.PDAnvil:62
> ------------------------------------------------------------------------
>
> It simply hangs forever. The java process is running, and who knows,
> maybe it even broke in main as promised, but the jde-db doesn't
> seem to realize it.
>
> My configuration:
>
> Stock emacs from RedHat 6.0 on Linux i386: (gnu-emacs 20.3.1)
> Patch to speedbar.el necessary to avoid c-frame error
> jde-2.1.6beta20 (doesn't work with 2.1.5 either)
>
> The following JDK's show this problem:
>
> * All of Sun's 1.2.2 releases (1.2.2.rc1, 1.2.2.rc2, 1.2.2)`
>
> The following JDK's do not show this problem:
>
> * Blackdown's 1.2 pre-releases (1.2-pre-v1, 1.2-pre-v2)
[snip]
The Sun releases, and Blackdown's RC4, contain the JPDA. The version
of jdb in these releases generate slightly different output, which
confuses JDE. There are two things you can do to fix this (choose one
or the other, not both).
1) The JDK releases also contain the old debugger, under the name
oldjdb. You can customize the variable jde-db-debugger to
"oldjdb" and it will work.
2) You can use JDEbug. My experience is that it's not quite ready for
prime time in Linux. Also, since you're a fellow menu-hater, I'll
bet you won't like its interface much. I know I don't. If you
want to try it, the documentation is in the ReleaseNotes.txt file.
Read it all, starting at 2.1.6 beta 5, and be prepared to come back
here for help.
--
Alan Hadsell
"Whatever does not kill me makes me stranger".
