This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH v6] Events when inferior is modified
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Nick Bull <nicholaspbull at gmail dot com>, gdb-patches at sourceware dot org
- Date: Thu, 25 Sep 2014 11:14:51 +0100
- Subject: Re: [PATCH v6] Events when inferior is modified
- Authentication-results: sourceware.org; auth=none
- References: <5419C597 dot 4000300 at gmail dot com>
On 17/09/14 18:32, Nick Bull wrote:
> [Resending because the previous discussion petered out without achieving signoff. The patch is identical to before except where line numbers have changed as the mainline has moved on.]
> This patch was originally submitted a few months ago; at that time it
> was looked at by Phil Muldoon and others, and there were no outstanding
> comments. I've updated it to take account of mainline changes, but
> otherwise it is unchanged.
> "This patch adds new observers, and corresponding Python events, for
> various actions on an inferior: calling a function (by hand),
> modifying registers or modifying memory.
> A use case for these events is that by flagging these occurrences, it
> can be noticed that the execution of the program is potentially
> 'dirty'. (Hence why the notification doesn't carry information about
> what was modified; for my purposes it's enough to know that /a/
> change has happened.)"
Can a global maintainer please look at this and give a sign-off? Just a
straight yes or no will do. I have already reviewed it and asked
several times for a sign-off. Nick has been very patient, and I think
at this point it is becoming somewhat annoying to pester for someone
to let Python patches through.