-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK.
I just wanted to serialize my thoughts here.
In the past I have not used debuggers. Primarily because I knew all of my
source code and understood what was going on. Recently I have been working on a
lot of projects where I don't know the code.... thus I find myself wanting to
play with jde-bug.
It seems like jde-bug is a little rough around the edges for new users.
Specifically there are some things it should catch when thing fail.
I mean when things work, they work great but when things fail, they fail
silently and without any debug information.
This is one area of improvement.
The other main area isn't really our fault but the VMs. It seems like the JDK
1.3 VM has problems in a lot of places. (I can't put a breakpoint in main() ).
Does anyone know how the 1.4 VM behaves? I can't run it for a number of
reasons.
Has anyone thought about integrating this with the ECB?
Could we add the jde-bug-menu to the other buffers? (CLI, Process, Local
Variables, etc).
Also. It seems like we should be able to handle things a little better when
things go wrong. If the JDEBug process terminates with an error. We should
probably display this to the user.
Anyway... I will probably grab the latest beta and play with this.
This should allow me to work on patches as I break it.
Other than that everything seems great! After all this was just constructive
criticism. :)
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/
Did you hear why they're using Windows 2000 as a prison guard? Because it
always locks up!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE79aDPAwM6xb2dfE0RAnqQAKCHa2Pv8RqLIUCae9wtxNIuFvLWbACgyPwy
T7PSciLzaJ4tJT+/qrKC9vM=
=O67r
-----END PGP SIGNATURE-----
