From: Keith Seitz <keiths@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Hui Zhu <teawater@gmail.com>, Hui Zhu <hui_zhu@mentor.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix dprintf work not right if it is pending
Date: Mon, 08 Apr 2013 07:20:00 -0000 [thread overview]
Message-ID: <51609773.9040009@redhat.com> (raw)
In-Reply-To: <515EF6A3.2080704@redhat.com>
On 04/05/2013 09:06 AM, Pedro Alves wrote:
> Thanks for the help Keith. Much appreciated.
I'm not exactly sure I would call this "helping." I think I created more
work than I actually saved. My apologies for that. That certainly wasn't
my intent.
> I think we want this:
>
> static void
> dprintf_re_set (struct breakpoint *b)
> {
> breakpoint_re_set_default (b);
>
> /* This breakpoint could have been pending, and be resolved now, and
> if so, we should now have the extra string. If we don't, the
> dprintf was malformed when created, but we couldn't tell because
> we can't extract the extra string until the location is
> resolved. */
> if (b->loc != NULL && b->extra_string == NULL)
> error (_("Format string required"));
>
> if (b->extra_string != NULL)
> update_dprintf_command_list (b);
> }
Yeah, that's good. Me likey. That was more like what I have in my sandbox.
> You mean, only update the command list if there isn't one before
> (because the breakpoint was pending before) ?
Yeah, I did mean that. Thank you to both you and Hui for clarifying why
this is necessary.
Thank you for your review of my review, too!
Keith
next prev parent reply other threads:[~2013-04-06 21:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 7:39 Hui Zhu
2013-03-22 12:40 ` Yao Qi
2013-03-25 1:00 ` Keith Seitz
2013-03-25 2:14 ` Yao Qi
2013-03-26 14:55 ` Hui Zhu
2013-03-28 17:07 ` Keith Seitz
2013-03-29 15:50 ` Hui Zhu
2013-04-03 3:34 ` Keith Seitz
2013-04-04 18:42 ` Hui Zhu
2013-04-05 18:30 ` Pedro Alves
2013-04-08 7:20 ` Keith Seitz [this message]
2013-04-08 17:57 ` Pedro Alves
2013-04-08 9:34 ` Hui Zhu
2013-04-08 14:35 ` Hui Zhu
2013-04-08 18:34 ` Pedro Alves
2013-04-09 15:28 ` Hui Zhu
2013-04-09 15:28 ` Pedro Alves
2013-04-10 15:57 ` Hui Zhu
2013-04-10 16:12 ` Hui Zhu
2013-04-11 5:46 ` Joel Brobecker
2013-04-11 17:03 ` Pedro Alves
2013-04-12 12:21 ` Hui Zhu
2013-03-25 8:25 ` Hui Zhu
2013-03-25 8:28 ` Yao Qi
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=51609773.9040009@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=palves@redhat.com \
--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