From: Jason Spiro <jasonspiro4@gmail.com>
To: gdb-patches@sources.redhat.com
Subject: stl-views.gdb slightly updated (was: modest, but very useful set of stl commands (gdb) - covers most stl containter)
Date: Wed, 27 Aug 2008 13:31:00 -0000 [thread overview]
Message-ID: <loom.20080826T144534-751@post.gmane.org> (raw)
In-Reply-To: <18353.10305.254004.27909@kahikatea.snap.net.nz>
Nick Roberts <nickrob <at> snap.net.nz> wrote:
[...]
> Are you claiming sole authorship. I have seen a very similar list at
> http://www.archivum.info/gnu.g++.help/2007-04/msg00030.html
> attributed to Tom Malnar (April 18, 2007).
Both sets of macros look similar because both sets of macros were made to
print STL containers. But from looking at the code, it looks like Dan wrote
his macros on his own and didn't copy from Tom's.
By the way, you can get a slightly improved version of stl-views.gdb on the
web now. Go to http://github.com/nitay/etc/tree/master/common/gdbinit and
click "raw" at the top-right corner to download.
prev parent reply other threads:[~2008-08-27 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 4:39 modest, but very useful set of stl commands (gdb) - covers most stl containter Dan C Marinescu
2008-02-12 5:02 ` Nick Roberts
2008-08-27 13:31 ` Jason Spiro [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=loom.20080826T144534-751@post.gmane.org \
--to=jasonspiro4@gmail.com \
--cc=gdb-patches@sources.redhat.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