This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Unfinished projects
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Stan Shebs <shebs at apple dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 15 Apr 2005 11:45:54 +0300
- Subject: Re: Unfinished projects
- References: <425EBC8F.4030405@apple.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 14 Apr 2005 11:55:11 -0700
> From: Stan Shebs <shebs@apple.com>
>
> Andrew's sudden departure from GDB maintenance
Did he really depart? Is that departure final or just temporary, and
if the latter, for how much time?
> seems to left a
> large number of projects in mid-process; as I'm picking through
> the latest sources trying to figure out how to merge with Apple's
> bits, it's very confusing as to how the new way is supposed to
> work when it's not documented anywhere and there's maybe only
> one example of a configuration using it.
I agree with Daniel: please list the problems and issues you need to
resolve, and let's deal with them one by one.
> So my question is - what should we do about all these? Are
> some of these intrinsically impossible to complete without
> the right collection of hardware? If so, then maybe we need
> to get tougher about dropping support for some targets, or
> else abandon the projected change.
I think we need to answer these questions on the per issue basis.
> I'd like to work on updating the GDB internals manual too, for my
> own understanding if nothing else; should I describe old ways, new
> ways, or both?
Obviously, I'd be the first to applaud the documentation effort (if
you need any help, please tell). In general, I agree with Mark here:
let's document the new ways, and only mention the old ones where it's
important for those who convert from widely used old ways.