From: "Matthew McCormick (thewtex)" <matt@mmmccormick.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: archer@sourceware.org
Subject: Re: [Archer] [PATCH 1/3] [python] Create gdb.pretty package.
Date: Mon, 18 Jan 2010 16:20:00 -0000 [thread overview]
Message-ID: <f23d1cbc1001180820x5a794127qb69e7ae603832ebb@mail.gmail.com> (raw)
In-Reply-To: <20100118080516.GL5800@adacore.com>
On Mon, Jan 18, 2010 at 2:05 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> A gdb.pretty Python package for holding code common for using Python
>> pretty-printers.
>
> Any reason why this is not submitted to gdb-patches? There is a modest
> ongoing development effort to provide pretty-printers for the GDB types,
> and we would very likely use this code.
>
Joel, the work to create gdb-gdb.py looks cool, and this would be
helpful there too.
My patches were based off archer-tromey-python, so I thought this was
the right place to post it, but if I can get it upstream by submitting
to gdb-patches, I will do so.
These are the beginning, and other patches are in the queue for
submission. I hope to send a screencast demonstrating the goal they
are reaching to this mailing list soon.
prev parent reply other threads:[~2010-01-18 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 15:00 [PATCH 1/3] [rfc][python] Create gdb.python package Matt McCormick
2009-12-31 15:00 ` [PATCH 2/3] [python] Create gdb.pretty.register Matt McCormick
2009-12-31 15:00 ` [PATCH 3/3] [python] Create pretty-printer lookup_function classes Matt McCormick
2010-01-18 3:43 ` [PATCH 2/3] [python] Create gdb.pretty.register Matthew McCormick (thewtex)
2010-01-18 7:57 ` [PATCH 3/3] [python] Create pretty-printer lookup_function classes Matt McCormick
2010-01-18 7:57 ` [PATCH 2/3] [python] Create gdb.pretty.register Matt McCormick
2010-01-18 7:57 ` [PATCH 1/3] [python] Create gdb.pretty package Matt McCormick
2010-01-18 8:05 ` [Archer] " Joel Brobecker
2010-01-18 16:20 ` Matthew McCormick (thewtex) [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=f23d1cbc1001180820x5a794127qb69e7ae603832ebb@mail.gmail.com \
--to=matt@mmmccormick.com \
--cc=archer@sourceware.org \
--cc=brobecker@adacore.com \
/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).