From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] dynamic printf
Date: Wed, 29 Feb 2012 18:21:00 -0000 [thread overview]
Message-ID: <83k435cxf3.fsf@gnu.org> (raw)
In-Reply-To: <4F4DCDD5.2040807@earthlink.net>
> Date: Tue, 28 Feb 2012 23:03:49 -0800
> From: Stan Shebs <stanshebs@earthlink.net>
>
> This patch implements a "dynamic printf", which is basically a
> breakpoint with a printf;continue as its command list - but with
> additional features that make it more interesting.
Thanks. I cannot say I like the name, though: the "dynamic" part has
no mnemonic value at all.
> + add_cmd ("agent-printf", class_maintenance, agent_printf_command,
> + _("Translate an expression into remote "
> + "agent bytecode for evaluation."),
> + &maintenancelist);
This new command seems to be undocumented.
> + add_setshow_enum_cmd ("dprintf-style", class_support,
> + dprintf_style_enums, &dprintf_style, _("\
> +Set the style of usage for dynamic printf."), _("\
> +Show the style of usage for dynamic printf."), _("\
> +Choose the style of usage for dynamic printf.\n\
How about listing the available styles with one line of description
for each one?
> +@item call
> +@kindex dprintf-style call
> +Handle the output by calling your program's @code{printf} function.
> +(This expects @code{printf} to have been linked into the program.)
And what happens if it isn't?
This needs a NEWS entry.
Thanks.
next prev parent reply other threads:[~2012-02-29 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 9:14 Stan Shebs
2012-02-29 10:28 ` Andreas Schwab
2012-03-13 23:09 ` Stan Shebs
2012-03-14 14:47 ` Marc Khouzam
2012-03-14 15:28 ` Tom Tromey
2012-02-29 16:16 ` Joel Brobecker
2012-03-13 23:15 ` Stan Shebs
2012-03-13 23:40 ` Joel Brobecker
2012-02-29 18:21 ` Eli Zaretskii [this message]
2012-03-13 23:20 ` Stan Shebs
2012-03-01 14:04 ` Hui Zhu
2012-03-04 6:31 ` Hui Zhu
2012-03-08 21:08 ` Tom Tromey
2012-03-13 23:51 ` Stan Shebs
2012-03-14 15:24 ` Tom Tromey
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=83k435cxf3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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