This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Convenience functions (was: Re: New scope checking patch)
- From: Daniel Jacobowitz <drow at false dot org>
- To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, Rob Quill <rob dot quill at gmail dot com>, gdb-patches at sourceware dot org
- Date: Tue, 4 Nov 2008 17:23:14 -0500
- Subject: Re: Convenience functions (was: Re: New scope checking patch)
- References: <baf6008d0801300405i47646b05pdb799d32ab71e005@mail.gmail.com> <u1w7zxjid.fsf@gnu.org> <8f2776cb0801301557t2e265b62u56d6df7cbcec1c84@mail.gmail.com> <utzkuws6q.fsf@gnu.org> <baf6008d0807271645o7d03dd94rd5b3f0d08302085a@mail.gmail.com> <m38wvk77qd.fsf@fleche.redhat.com> <baf6008d0807291404x255213b7id79efc6939d92eb1@mail.gmail.com> <m3bq0g59md.fsf@fleche.redhat.com> <20081023134150.GA21234@caradoc.them.org> <1225834560.20764.8.camel@localhost.localdomain>
On Tue, Nov 04, 2008 at 07:35:59PM -0200, Thiago Jung Bauermann wrote:
> Since Tromey mentioned that Rob's patch is not correct in its current
> form, I'm thinking of implementing it in python and use it to direct my
> choice of next python patches to post here (i.e., my next set of python
> patches would have the goal of making a scope checking script work).
> Then I could work on testcases and documentation. What do you think?
Sounds reasonable to me.
> The upside is that this will help focus the python submissions to
> enabling a useful functionality as soon as possible. The downside (or
> maybe it's not a downside at all) is that a scope checking feature is
> being asked by users, so it would mean that such python script would
> preferably be shipped in GDB releases...
Yes - we've got to get the mechanism to do that in place anyway.
--
Daniel Jacobowitz
CodeSourcery