From: sami wagiaalla <swagiaal@redhat.com>
To: archer@sourceware.org
Subject: Re: Python inferior control
Date: Wed, 01 Dec 2010 18:58:00 -0000 [thread overview]
Message-ID: <4CF69AC3.6090501@redhat.com> (raw)
In-Reply-To: <4C655CA0.8010205@redhat.com>
On 08/13/2010 10:54 AM, Phil Muldoon wrote:
> Hi,
>
> On the 23rd of August 2009 Oguz Kayral submitted an initial patch to
> implement GDB inferior notification events in Python. Since then the
> patch has bit-rotted somewhat. I've reconstituted this patch
> against current GDB head and attached it. I've not changed very much:
> renamed the files, re-ordered the Makefile.in and made some minor code
> changes so that it compiles.
>
I have started looking at this with the purpose of getting Oguz's work
upstream. I stated by removing bit rot from the patch that phil posted,
and making my own modifications to get things to conform to GDB coding
standards. I have also started addressing some of the issues that where
brought up on this thread and in reply to Oguz's original posts.
You can follow my progress on this branch on the archer repository:
archer-swagiaal-oguz
When I am finished I will reply to the emails here and post the patch on
gdb-patches so we can continue the discussion there.
Sami
prev parent reply other threads:[~2010-12-01 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 14:54 Phil Muldoon
2010-08-13 19:49 ` Tom Tromey
2010-08-26 15:02 ` Oguz Kayral
2010-08-26 20:28 ` Tom Tromey
2010-09-20 16:13 ` Matt Rice
2010-09-21 21:48 ` Tom Tromey
2010-08-15 17:42 ` Richard Ward
2010-08-26 20:23 ` Tom Tromey
2010-08-25 16:10 ` Phil Muldoon
2010-12-01 18:58 ` sami wagiaalla [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CF69AC3.6090501@redhat.com \
--to=swagiaal@redhat.com \
--cc=archer@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).