From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Ryan C. Gordon" <icculus@icculus.org>, gdb-patches@sourceware.org
Subject: Re: Data plugins for gdb...
Date: Fri, 08 Aug 2008 04:20:00 -0000 [thread overview]
Message-ID: <1218169143.11103.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20080808003020.GA17221@caradoc.them.org>
On Thu, 2008-08-07 at 20:30 -0400, Daniel Jacobowitz wrote:
> On Fri, Aug 08, 2008 at 01:23:35AM +0200, Ryan C. Gordon wrote:
> >
> > I spent a few hours hacking something out as a proof of concept; I'd
> > appreciate some opinions from those that know better.
Heh, been there, done that. :-)
> The GDB project (particularly Vladimir, Tom, and Thiago) is in the
> process of adding Python support. One of the intended uses is just
> this same idea. They're still designing the command-line interface
> to it; I believe Thiago is currently looking into it.
Indeed I am.
> Vladimir's also
> made it work via MI, so that front-end GUIs can access this
> functionality too. There's more information on the PythonGDB wiki
> page.
I've been looking at Vladimir's code. It's interesting how his patch and
Ryan's converge in one thing, which is searching of a pretty-printer by
matching the string representation of the type with a string (or regexp
in the case of Vladimir's version) provided by the pretty-printer.
An alternative would be to add a new element to struct type pointing to
its pretty-printer (if any). I think this would be better, because then
you can be very specific about exactly which type you want to associate
with your semantically helpful visualizer. Think lookup_typename here,
which looks up a type within a lexical block (at least that's what its
description says).
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2008-08-08 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 23:24 Ryan C. Gordon
2008-08-08 0:31 ` Daniel Jacobowitz
2008-08-08 4:20 ` Thiago Jung Bauermann [this message]
2008-08-08 5:10 ` Ryan C. Gordon
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=1218169143.11103.30.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=icculus@icculus.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