From: Hui Zhu <teawater@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Let dprintf can be saved
Date: Mon, 22 Apr 2013 00:19:00 -0000 [thread overview]
Message-ID: <CANFwon0Hu6zqh_Ro5T_=Fxm-A0HyqyRkOp8RC-3MEVMOJh2hOg@mail.gmail.com> (raw)
In-Reply-To: <87fvymwkbi.fsf@fleche.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Sat, Apr 20, 2013 at 12:34 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Hui" == Hui Zhu <teawater@gmail.com> writes:
>
> Hui> +static void
> Hui> +dprintf_print_recreate (struct breakpoint *tp, struct ui_file *fp)
>
> This needs a short introductory comment.
> See the other print_recreate methods for examples.
Fixed.
>
> I think this patch could use a test case.
> It could be added wherever the existing "save" tests live.
OK. I will post a patch for it later.
Thanks,
Hui
>
> Tom
2013-04-18 Hui Zhu <hui@codesourcery.com>
PR gdb/15165
* breakpoint.c (dprintf_print_recreate): New.
(save_breakpoints): Let it not save dprintf commands.
(initialize_breakpoint_ops): Set dprintf_print_recreate.
[-- Attachment #2: dprintf-save.txt --]
[-- Type: text/plain, Size: 1180 bytes --]
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -13364,6 +13364,16 @@ dprintf_re_set (struct breakpoint *b)
update_dprintf_command_list (b);
}
+/* Implement the "print_recreate" breakpoint_ops method for dprintf. */
+
+static void
+dprintf_print_recreate (struct breakpoint *tp, struct ui_file *fp)
+{
+ fprintf_unfiltered (fp, "dprintf %s%s", tp->addr_string,
+ tp->extra_string);
+ print_recreate_thread (tp, fp);
+}
+
/* The breakpoint_ops structure to be used on static tracepoints with
markers (`-m'). */
@@ -15453,7 +15463,7 @@ save_breakpoints (char *filename, int fr
if (tp->ignore_count)
fprintf_unfiltered (fp, " ignore $bpnum %d\n", tp->ignore_count);
- if (tp->commands)
+ if (tp->type != bp_dprintf && tp->commands)
{
volatile struct gdb_exception ex;
@@ -15859,7 +15869,7 @@ initialize_breakpoint_ops (void)
ops->resources_needed = bkpt_resources_needed;
ops->print_it = bkpt_print_it;
ops->print_mention = bkpt_print_mention;
- ops->print_recreate = bkpt_print_recreate;
+ ops->print_recreate = dprintf_print_recreate;
}
/* Chain containing all defined "enable breakpoint" subcommands. */
next prev parent reply other threads:[~2013-04-20 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 17:04 Hui Zhu
2013-04-19 18:33 ` Tom Tromey
2013-04-19 18:36 ` Keith Seitz
2013-04-22 0:19 ` Hui Zhu [this message]
2013-04-22 0:24 ` Hui Zhu
2013-04-22 23:26 ` Tom Tromey
2013-04-23 16:53 ` Hui Zhu
2013-04-24 14:34 ` Joel Brobecker
2013-04-24 14:35 ` Hui Zhu
2013-04-22 23:47 ` 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='CANFwon0Hu6zqh_Ro5T_=Fxm-A0HyqyRkOp8RC-3MEVMOJh2hOg@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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