Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vincent Benony <vbenony@nordnet.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: Using STL containers with GDB
Date: Tue, 22 Apr 2008 22:13:00 -0000	[thread overview]
Message-ID: <18446.23053.860176.935315@kahikatea.snap.net.nz> (raw)
In-Reply-To: <1208857199.6213.15.camel@bsr-desktop>

 > 	So, yesterday, I decided myself to look at the code of GDB. After a
 > quick look, I wrote this patch. I know that it's not very clean, and
 > that it makes many assumptions about STL containers, and that it cannot
 > be considered as a long term feature for GDB, but, believe me, it's very
 > very usefull !
 > 
 > 	Now, I can look at the content of list, vector, set, map, multiset,
 > multimap and string simply with the classic "print" command of GDB.

The Python branch appears to work for executables compiled with Gcc only.  I'm
curious to know if this approach will work for executables built using other
compilers?

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  parent reply	other threads:[~2008-04-22 21:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 12:29 Vincent Benony
2008-04-22 14:41 ` Daniel Jacobowitz
2008-04-22 14:49   ` Vincent Benony
2008-04-22 17:51     ` Thiago Jung Bauermann
2008-04-22 18:37       ` Vladimir Prus
2008-04-22 22:13 ` Nick Roberts [this message]
2008-04-22 22:56   ` Daniel Jacobowitz
2008-04-23  6:49     ` Vincent Bénony
2008-04-23  8:53       ` Eli Zaretskii
2008-04-23  9:29         ` BENONY Vincent
2008-04-23 10:12       ` Nick Roberts
2008-04-23 12:22         ` Daniel Jacobowitz
2009-05-27 20:27 Using STL Containers With GDB Ken Lauterbach
2009-05-27 21:24 ` Paul Pluzhnikov

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=18446.23053.860176.935315@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sourceware.org \
    --cc=vbenony@nordnet.fr \
    /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