==> Are you using the HotSpot VM? jdb appears to be broken with it. Try
==> switching back to the classic VM. For more information see:
==>
==> http://developer.java.sun.com/developer/techDocs/SearchData/dd/HotSpot/15.html
==>
==> Allan
The JDB that ships with the JDK is built on the sun.tools.debug debugger
interface. This interface is deeply classic VM specific, so it will
not work under HotSpot or any other VM that is not a derivative of the
classic VM. For this reason and other inherent problems in sun.tools.debug
we have developed a new debugger architecture for Java: the Java Platform
Debugger Architecture (JPDA). This DOES work under HotSpot (although the
support is labeled beta-quality at this point). There is an unsupported
example port of JDB to this new architecture which is available in source
and binary form as part of the JPDA beta download:
http://developer.java.sun.com/developer/earlyAccess/jpda/index.html
I have no idea if this will be compatible with JDE, but if you try it out
I'd love to hear. We will be working on tighter JPDA-JDE integration this
summer - but that doesn't help you now ;-)
-Robert
==> Kenneth J. Goldman <[EMAIL PROTECTED]> wrote in message
==> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
==> > I just installed the JDE with JDK 1.2.1. Everything works
==> > very well, except the debugger. When starting the jdb, I
==> > get the error:
==> >
==> > Initializing jdb...
==> > Failed accessing debugging session on <machine name>: invalid password
==> >
==> > This happens even when invoking the debugger from bash directly.
==> >
==> > I understand there is a -password option to jdb and that starting
==> > the interpreter with -Xdebug is supposed to print the password
==> > required, but it doesn't seem to.
==> >
==> > Any suggestions?
==> >
==> > -Ken
==>
==>
