From: Siva Chandra <sivachandra@google.com>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Debug Methods in GDB Python
Date: Fri, 13 Dec 2013 19:25:00 -0000 [thread overview]
Message-ID: <CAGyQ6gycVe2-32djRDfYBWjGQ2LLwqzzR1q0iFBoW+zG5vttvg@mail.gmail.com> (raw)
In-Reply-To: <CAP9bCMTDjJ_ZEqhSbZAwGu8CswZJsLu7UrSL5JeY72bb9AO-qQ@mail.gmail.com>
> On Fri, Dec 6, 2013 at 3:24 PM, Siva Chandra <sivachandra@google.com> wrote:
> I have removed DEFAULT_DEBUG_METHOD_GROUP from the code in my latest
> patch. However, there is one reference to it in the brief (really
> brief!) doc change I have in the patch [1]. About grouping in
> libstdc++, is it not doing a grouping within what is facilitated by
> the pretty printing API?
dje > Not sure I understand the question.
libstdc++ pretty printers use the pretty printing API provided by GDB
Python. So, if we are to compare debug methods API to something,
shouldn't we be comparing with the pretty printing API? About the
matching API provided by the debug methods API in my patch, there
isn't anything specific at all. The users can match class name and
method name in whatever manner they please. If they like the libstdc++
pretty printers way, then they can do it that way.
next prev parent reply other threads:[~2013-12-13 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 22:41 Siva Chandra
2013-11-26 3:22 ` Siva Chandra
2013-12-06 6:31 ` Doug Evans
2013-12-06 23:24 ` Siva Chandra
2013-12-12 5:26 ` Doug Evans
2013-12-13 19:25 ` Siva Chandra [this message]
2013-12-16 17:56 ` Doug Evans
2013-12-16 22:43 ` Siva Chandra
2014-01-01 12:23 ` Siva Chandra
2014-01-03 18:52 ` Doug Evans
2014-01-08 0:49 ` Siva Chandra
2014-01-09 19:01 ` Doug Evans
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=CAGyQ6gycVe2-32djRDfYBWjGQ2LLwqzzR1q0iFBoW+zG5vttvg@mail.gmail.com \
--to=sivachandra@google.com \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).