Hi Paul,
I'm using version JDE-2.2.6 and use JDEbug on a regular basis and
experience no problems.
I also would be more interested in seeing further JDEbug enhancements
over coding engine enhancements. On my wish list is having brief
documentation describing each debugging command and whether or not it
is thought to be fully functional. With this information, I would start
trying out more of the commands and helping with debugging. My favorite
command would be a fully functional "evaluate expression". I know you
have said in the past that JPDA doesn't support this, but there must be
some way to at kludge it as I know of other JPDA based debuggers, e.g.
JBuilder Professional, that support this functionality.
Thanks so much for your efforts.
Chuck
> -----Original Message-----
> From: paulk [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 05, 2001 10:21 AM
> To: klaus.berndl; klaus.berndl; jde
> Cc: paulk
> Subject: Re: AW: AW: JDebug Improvement Suggestion
>
>
> At 10:45 AM 4/5/01 +0200, [EMAIL PROTECTED] wrote:
> [snip]
> >No, you are definitely not the only guy able to use JDEBug :-)
> >IMHO the problems JDEBUG getting startet will go to nearly zero
> >because many of these problems are related not using the most
> >recent JDK (means < 1.3.0), some problems getting the
> >classic-VM with JDK 1.3 under Windows NT to run and some
> >problems with the Hotspot-VM under Solaris. Also the JPDA-debugging
> >standard of Sun is realtive new.
> >But lets wait soem month and most people will use JDK >= 1.3.02,
> >problems oh hotspot-vms will reduce and JDEBug will start for most
> >user without any problems. At least i hope so...:-)
> >Any other opinion?
> >
>
> You and I have the same hope and expectation.
>
> >But: For a really good IDE (for any language) a good
> (graphical if possible)
> >debugger is essential so please do not stop development of JDEBug.
> >In contrary: Please correct me but IMO you have much more
> enhanced and
> >improved in the last months the "coding-engine" of JDE (means adding
> >features for
> >most conveniant editing and compiling java-code) than the
> JDEbug. IMHO the
> >"coding-engine" is good enough (of course nothing is good
> enough, but i
> >believe you know
> >what i mean :-) and now some of your power should flow back
> into the JDEBug
> >because
> >IMHO (please correct me if i say nonsens) it seems there is
> a little bit
> >develoment-stagnancy for JDEBug??!!
>
> Absolutely, about a year ago, the advent of semantic plus a host of
> contributions from JDE users diverted my attention from
> JDEbug. I have
> felt very bad all along about neglecting JDEbug, which I regard as
> basically an early beta version, and have been anxious all
> along to get
> back to it. But the recent string of reports of JDEbug
> hanging at startup
> plus the absence of feature requests and comments (contrasted
> with the many
> requests in the editing area) made me wonder if anyone was
> using JDEbug
> and, if not, whether it was worthwhile investing any further time in
> JDEbug. Your response plus that of many others has renewed my
> determination
> to develop JDEbug into a robust and easy-to-use debugging tool.
>
> - Paul
>
