Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: ghost@cs.msu.su, gdb@sources.redhat.com
Subject: Re: Variable objects and STL containers
Date: Tue, 05 Feb 2008 13:18:00 -0000	[thread overview]
Message-ID: <20080205131800.GB10652@caradoc.them.org> (raw)
In-Reply-To: <200802051131.m15BV7kd006854@brahms.sibelius.xs4all.nl>

On Tue, Feb 05, 2008 at 12:31:07PM +0100, Mark Kettenis wrote:
> > We discussed using Python scripting for that; in fact, I have a patch locally
> > that will make 
> > 
> >         -var-evaluate-expression V 
> > 
> > for a vector print something like:
> > 
> >         [1,2,3]
> > 
> > I'm working on making those element the children of the variable object,
> > but it's not done yet.
> 
> Still this means that you'll need to write python code for each and
> every STL implementation, and play catchup whenever the implementation
> is changed.  I guess the only way to get this to work is to connvince
> the GCC people to maintain the python code together with libstdc++.

Right.  That's what I would like to happen; and since GCC is both a
GNU project and widely used with GDB, I think it will be easy to
convince them.  I envision these scripts going in
/usr/share/gdb/packages or something similar to that.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-02-05 13:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  6:01 Nick Roberts
2008-02-05  6:17 ` Vladimir Prus
2008-02-05  6:34   ` Nick Roberts
2008-02-05  6:56     ` Vladimir Prus
2008-02-05 13:16     ` Daniel Jacobowitz
2008-02-15  9:24       ` Nick Roberts
2008-02-17  0:19         ` Nick Roberts
2008-02-17  7:14           ` Vladimir Prus
2008-02-17 19:55             ` Nick Roberts
2008-02-18  8:12               ` Vladimir Prus
2008-02-19 16:31         ` Daniel Jacobowitz
2008-02-05 11:31   ` Mark Kettenis
2008-02-05 12:03     ` Vladimir Prus
2008-02-05 13:18     ` Daniel Jacobowitz [this message]
2008-02-08  0:53   ` Nick Roberts
2008-02-08  6:47     ` Vladimir Prus
2008-02-10  4:28       ` Nick Roberts
2008-02-10  7:11         ` Vladimir Prus
2008-02-10 17:52           ` Daniel Jacobowitz
2008-02-10 18:14             ` Vladimir Prus
2008-02-10 19:45             ` Doug Evans
2008-02-10 19:44           ` Doug Evans
2008-02-10 20:05             ` Vladimir Prus
2008-02-10 21:02           ` Nick Roberts
2008-02-11  9:12             ` Vladimir Prus
2008-02-11 13:07               ` Daniel Jacobowitz
2008-02-11 20:28               ` Nick Roberts

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=20080205131800.GB10652@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=mark.kettenis@xs4all.nl \
    /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