From: Doug Evans <dje@google.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] tracepoint: add new trace command "printf"[0] gdb
Date: Mon, 03 Jan 2011 19:21:00 -0000 [thread overview]
Message-ID: <AANLkTik=K4Dk-Mkc5P7DDofzqwThhE6LvCM4rT-U_LNt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimhMH+qUE1NmQ+f6+L8BcEU+k07eU+M9B-gLsrk@mail.gmail.com>
On Mon, Jan 3, 2011 at 8:29 AM, Hui Zhu <teawater@gmail.com> wrote:
> Hi,
>
> I add a new patch add new trace command "printf".
> This printf is same with the simple gdb command, it can do formatted
> output. But it will happen in gdbserver part when it break by a
> tracepoint.
> Then the user can get the format value that he want in tracepint. It
> will be more easy and clear to handle the bug sometimes.
One could do this with a breakpoint and attaching commands to the
breakpoint too, right?
Or are they too cumbersome for the intended use case?
[Extending tracepoints like this doesn't seem justified yet, so I'm
just looking for more data.]
next prev parent reply other threads:[~2011-01-03 19:21 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 [this message]
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
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='AANLkTik=K4Dk-Mkc5P7DDofzqwThhE6LvCM4rT-U_LNt@mail.gmail.com' \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).