From: Keith Seitz <keiths@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: 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: Wed, 03 Apr 2013 03:34:00 -0000 [thread overview]
Message-ID: <515B1DF7.3090705@redhat.com> (raw)
In-Reply-To: <CANFwon3OdcsC3PQRwteYPKiBYFFKGPcOfMVcc4Fx8XdjZ=-pQw@mail.gmail.com>
On 03/29/2013 12:42 AM, Hui Zhu wrote:
>>> + breakpoint_re_set_default (b);
>>> +
>>> + if (b->extra_string != NULL)
>>> + update_dprintf_command_list (b);
>>> +}
>>> +
>>
>>
>> This will update the command list every time breakpoints are reset and could
>> be limited to only those needing updating. Is there perhaps a reason to
>> always do this?
>
> I think it need, because it need to generate different commands with
> different status for example:
> if (target_can_run_breakpoint_commands ())
> printf_line = xstrprintf ("agent-printf %s", dprintf_args);
>
I'm not understanding this example. How is this likely to change
whenever breakpoints are reset? Is there perhaps a way to add a test to
demonstrate this requirement?
Otherwise, this patch looks good to me, and recommend that a maintainer
give this a final review.
Keith
next prev parent reply other threads:[~2013-04-02 18:05 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 [this message]
2013-04-04 18:42 ` Hui Zhu
2013-04-05 18:30 ` Pedro Alves
2013-04-08 7:20 ` Keith Seitz
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=515B1DF7.3090705@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.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