From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] prec: add a switch for memory doesn't record query
Date: Sun, 20 Jun 2010 15:08:00 -0000 [thread overview]
Message-ID: <83hbkxg2va.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTim8XbQV_b6iLXQmeatJa6y6xPgAnszMrM2rhdbC@mail.gmail.com>
> From: Hui Zhu <teawater@gmail.com>
> Date: Sun, 20 Jun 2010 14:01:38 +0800
> Cc: gdb-patches@sourceware.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.
A slight rewording:
@kindex set record memory-query
@item set record memory-query
Control the behavior when @value{GDBN} is unable to record memory
changes caused by an instruction. If ON, @value{GDBN} will query
whether to stop the inferior in that case.
If this option is OFF (the default), @value{GDBN} will automatically
ignore the effect of such instructions on memory. Later, when
@value{GDBN} replays this execution log, it will mark the log of this
instruction as not accessible, and it will not affect the replay results.
next prev parent reply other threads:[~2010-06-20 15:08 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
2010-06-20 15:08 ` Eli Zaretskii [this message]
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=83hbkxg2va.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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