-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
"Scott Evans" <[EMAIL PROTECTED]> writes:
> I finally got fed up trying to debug servlet-type processes with println
> statements so I'm going "debugger".
I think the killer combo could be:
JDEBug/JPDA
Tomcat class reloading
Cactus unit testing
... I am going to play with that today.
I wills send off a report :)
> I got jdb working okay but of course its interface is a little clunky,
> especially compared to a nice in-your-editor display.
>
> So I set up JDEbug and gave it a go. Right away I said "yes! this rocks!" but
> unfortunately the performance seems pretty awful compared to command-line jdb.
It is also kind of quirky... you will see what I mean :)
> Variable queries take ~30 seconds to come back; stepping from line to line is
> very slow as well. This all works as one might expect (i.e. "quickly") in
> command-line jdb.
How are you running command-line in JDB? Are you using TCP or shared memory or
in-VM???
> I'm running on Win2000, using shared memory to attach to a running process.
>
> Is this known behavior for JDEbug? If not, any advice?
<snip/>
Yes... it is kind of sluggish.
Kevin
- --
Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] )
Location - San Francisco, CA, Cell - 415.595.9965
Jabber - [EMAIL PROTECTED], Web - http://relativity.yi.org/
Resistance is *not* futile!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE8WcDmAwM6xb2dfE0RAincAKCLMe/rNJRMVGyFzTMoexESGUsRBgCgyBfv
clJ5OE8PbnUyRcOmwjbHruk=
=I2Qu
-----END PGP SIGNATURE-----
