From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] prec: add a switch for memory doesn't record query
Date: Sun, 20 Jun 2010 06:02:00 -0000 [thread overview]
Message-ID: <AANLkTim8XbQV_b6iLXQmeatJa6y6xPgAnszMrM2rhdbC@mail.gmail.com> (raw)
In-Reply-To: <83d3voiyjv.fsf@gnu.org>
Thanks Eli. What about following?
@kindex set record memory-query
@item set record memory-query
Control the behavior when @value{GDBN} cannot record memory change
of next instruction. If ON, @value{GDBN} will query when it cannot
record memory change of next instruction.
If this option is OFF(the default), @value{GDBN} will auto ignore this
issue. When @value{GDBN} replay to this execution log, it will mark
this log as not accessible, then it will not affect the replay.
Hui
On Fri, Jun 18, 2010 at 15:34, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Fri, 18 Jun 2010 12:59:49 +0800
>>
>> Some words in the doc is not very well. Did some small change.
>
> Thanks.
>
>> +Control the behavior when PREC cannot record memory change of next
>> +instruction. If ON, @value{GDBN} will query when it cannot record
>> +memory change of next instruction.
>
> First, please don't use "PREC", this is not a term we use in the
> manual.
>
> Second, I think a short explanation of why this could happen is in
> order.
>
>> +If this option is OFF(the default), @value{GDBN} will auto ignore this
>> +issue. It can handle it with itself.
>
> This is too mysterious. I think we should have at least some
> explanation of what this auto handling does. Otherwise, the reader
> will not be able to decide whether to set this on or not.
>
>
next prev parent reply other threads:[~2010-06-20 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 2:38 Hui Zhu
2010-06-18 5:00 ` Hui Zhu
2010-06-18 7:34 ` Eli Zaretskii
2010-06-20 6:02 ` Hui Zhu [this message]
2010-06-20 15:08 ` Eli Zaretskii
2010-06-20 16:30 ` Hui Zhu
2010-06-20 17:30 ` Eli Zaretskii
2010-06-25 6:13 ` 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=AANLkTim8XbQV_b6iLXQmeatJa6y6xPgAnszMrM2rhdbC@mail.gmail.com \
--to=teawater@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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