This is the mail archive of the
mailing list for the Java project.
Re: Overview of interpreted debugging design
- From: Tom Tromey <tromey at redhat dot com>
- To: Keith Seitz <keiths at redhat dot com>
- Cc: GCJ Mailing List <java at gcc dot gnu dot org>
- Date: 27 May 2005 13:14:43 -0600
- Subject: Re: Overview of interpreted debugging design
- References: <email@example.com>
- Reply-to: tromey at redhat dot com
>>>>> "Keith" == Keith Seitz <firstname.lastname@example.org> writes:
Keith> The back-end is segregated into several packages which deal with the
Keith> most important areas of functionality:
Wow, there's a lot more than I realized.
Keith> So, unless people want more specific information on anything, I am ready
Keith> to start the review process. I would think the easiest place to start
Keith> would be the transport layer (gnu.gcj.jdwp.transport), but I am willing
Keith> to start wherever people would like.
You should set the agenda here.
I'm not overly concerned with the libgcj-independent details of the
JDWP code -- I'm sure you know a lot more about this than any of us.
I'm thinking the review can center on a few things:
- Is there code that can/should be in classpath, and if so should we
try to do that first in order to avoid renaming everything later.
- What changes are needed to existing parts of libgcj
- General style conformance; second look for big gotchas