From: Michael Snyder <msnyder@vmware.com>
To: Doug Evans <dje@google.com>
Cc: Hui Zhu <teawater@gmail.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] tracepoint: add new trace command "printf"[0] gdb
Date: Wed, 05 Jan 2011 18:18:00 -0000 [thread overview]
Message-ID: <4D24B5D3.3040202@vmware.com> (raw)
In-Reply-To: <AANLkTimCwZtpRn4Q3eKATbVHpGreaaFsdjPPizoqQkvS@mail.gmail.com>
Doug Evans wrote:
> On Mon, Jan 3, 2011 at 10:18 PM, Doug Evans <dje@google.com> wrote:
>> [One might think why not just add printf (and whatever else) to
>> tracepoints and leave it at that. Tracepoints to me convey a specific
>> use-case and I'm not sure we should muddy that up. But for now I
>> suppose printf could be sufficiently useful, so I'm not opposed to the
>> patch (pragmatic hacks are sometimes useful enough to justify their
>> existence). This is not an approval though. I can see the patch
>> needs at least a few changes, but before reviewing it I'd like to make
>> sure there is general agreement on this approach. Someone else is
>> free to review and approve it of course.]
>
> I haven't heard comments from any other GMs.
> Does anyone have a problem with adding some kind of printf to tracepoints?
> Or does anyone have a problem with adding a new kind of command list
> to breakpoints that is executed on the target?
> [P.S. If you respond, IWBN to include your thoughts on why.]
> I'm inclined to go with having some kind of printf in tracepoints for now.
I don't quite understand the "use case" for printf in tracepoints.
next prev parent reply other threads:[~2011-01-05 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 16:29 Hui Zhu
2011-01-03 19:21 ` Doug Evans
2011-01-04 4:34 ` Hui Zhu
2011-01-04 6:19 ` Doug Evans
2011-01-04 12:07 ` Hui Zhu
2011-01-05 17:24 ` Doug Evans
2011-01-05 18:18 ` Michael Snyder [this message]
2011-01-06 6:42 ` Hui Zhu
2011-01-05 20:51 ` Stan Shebs
2011-01-06 6:43 ` Hui Zhu
2011-01-28 5:54 ` Hui Zhu
2011-02-04 15:59 ` Hui Zhu
2011-02-11 3:49 ` Hui Zhu
2011-02-11 18:45 ` Tom Tromey
2011-02-17 8:16 ` Hui Zhu
2011-02-21 8:18 ` Hui Zhu
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=4D24B5D3.3040202@vmware.com \
--to=msnyder@vmware.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@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