Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: GDB C plugin system, and STL container viewer as an example
Date: Fri, 23 May 2008 19:53:00 -0000	[thread overview]
Message-ID: <20080523143043.GA32366@caradoc.them.org> (raw)
In-Reply-To: <g16jrk$3r6$1@ger.gmane.org>

On Fri, May 23, 2008 at 06:20:36PM +0400, Vladimir Prus wrote:
> I don't see how you report that fact that the number of children of a
> varobj has changed. Without that, I'm not sure how useful MI display
> of vectors is. Am I missing something?

Just my two cents but... rather than encourage further work on the C
mechanism, is there anyone besides me who could start reviewing the
Python patches, so that we can converge on a single mechanism and get
it into the tree?  If everyone waits for me to get around to it, it's
going to be a while.

Vincent, are you at all interested in taking the code you've written
and integrating it with the gdb+python repository?  (If so, you'll
need a copyright assignment, if you haven't got one already.)

FYI, I am unlikely to be reviewing patches for the next week or two
unless my plans turn out to be much more boring than I expect :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-05-23 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 18:34 Vincent Benony
2008-05-23 19:30 ` Vladimir Prus
2008-05-23 19:53   ` Daniel Jacobowitz [this message]
2008-05-27 18:17     ` Vincent Bénony
2008-05-27 18:21       ` Thiago Jung Bauermann
2008-05-23 19:59   ` Vincent Benony
2008-05-23 20:31     ` Vladimir Prus
2008-05-23 20:39       ` Vincent Benony
2008-05-23 20:46         ` Vladimir Prus

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=20080523143043.GA32366@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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