>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
Paul> At 09:52 AM 10/1/00 GMT, you wrote:
>> Probably a stupid question, but how come the debugging environments
>> for applets and applications are not the same? I know from Forte
>> that it's possible - unfortunately I get a rash after 2 minutes of
>> using Forte and have to go get my emacs medication in a hurry.
Paul> Your question is quite reasonable. The JDE originally offered
Paul> only an interface to jdb as a debugging capability. Within the
Paul> last year, I have added a JPDA-based debugger, JDEBug, which was
Paul> developed with the help of the Sun JPDA team. I have not had
Paul> time to investigate whether it is possible to provide JDEbug
Paul> with the ability to debug applets that run in a browser or
Paul> appletviewer's vm. Theoretically it should be possible to attach
Paul> JDEbug to the browser or appletviewer vm. However, AFAIK, these
Paul> applications do not allow you to put the vm into the required
Paul> JPDA debug server mode. Any insight you can offer on this
I know the Forte GUI basically launches the regular VM, starting
execution somewhere in the Sun AppletViewer classes. They also use a
lot of magic arguments - presumably to attach to the process after it
has launced.
I never really took a close look at it, but I'm certainly able and
willing to do it, if all I have to do is feed you the info. I've never
been confortable with (e)lisp, and looking at the jde sources just
plain scares me :)
Paul> problem would be very welcome. You can certainly use JDEbug to
Paul> debug applets if you write the applets to be applications as
Paul> well, i.e., to include a main method and perhaps a wrapper frame
Paul> to contain the applet GUI.
I have tried this but it doesn't work well enough to be really useful.
Jesper
