Interpreted debugging with gcj/gij

[Tom Tromey]

>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:

Keith> The first obvious questions are administrative: How would
Keith> maintainers and contributors like to review patches and start the
Keith> rolling of the proverbial ball?

Keith> I can certainly send a follow-on message, explaining the
Keith> overall design of the back-end which was designed with an eye
Keith> on minimal impact on non- debugging performance and
Keith> VM-neutrality.

Yeah, this would be very helpful, so that folks can get an overview of
what is going on -- a context in which to review the patches.

Keith> The approach I've taken (and advocate) is to lay the foundation
Keith> and fill in the blanks -- there's a *lot* of them to fill in.

Sounds great.

As far as administrative stuff, the URLs Mark posted are a good start.
I think what we'll do is get you a cvs account, but just for (our)
convenience at first... send patches to the java-patches list (if you
have any changes outside of the runtime, those should be CCd to
gcc-patches), someone will review them, etc.  Typically we do this for
a while and then eventually you can just commit things in "your area"
on your own approval.

If there is code that could go in Classpath, it would be best to start
talking about that too.  What does it do, what should we name it,
those kinds of things.

Tom