From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, msnyder@vmware.com
Subject: Re: [Precord RFA/RFC] Check Linux sys_brk release memory in process record and replay.
Date: Tue, 09 Jun 2009 02:17:00 -0000 [thread overview]
Message-ID: <daef60380906081917k3eabe59an2ba2a2983c139d10@mail.gmail.com> (raw)
In-Reply-To: <daef60380905110006gaa1ac38r870f6be455a402fc@mail.gmail.com>
Ping.
On Mon, May 11, 2009 at 15:06, Hui Zhu<teawater@gmail.com> wrote:
> PING.
>
> On Thu, May 7, 2009 at 11:20, Eli Zaretskii <eliz@gnu.org> wrote:
>>> Date: Thu, 7 May 2009 10:21:04 +0800
>>> From: Hui Zhu <teawater@gmail.com>
>>> Cc: gdb-patches@sourceware.org, msnyder@vmware.com
>>>
>>> > I thought the problem was that replaying the execution log before the
>>> > sbrk point would be impossible, because (I thought) there's no way of
>>> > regaining back the memory the inferior gave up. Is this the problem
>>> > you are talking about? If so, that is not a fatal limitation, and it
>>> > certainly does not justify stopping the program and asking the user to
>>> > make some grave decision. The user just needs to be notified, when
>>> > she tries that, that she cannot reverse-replay the log past this
>>> > point. If the user never tries to replay past that point, she never
>>> > needs to know about the problem.
>>>
>>> I am not sure make inferior cannot continue is good or not. I think
>>> let user choice continue or stop is better.
>>
>> Well, what do others think?
>>
>
next prev parent reply other threads:[~2009-06-09 2:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 13:07 Hui Zhu
2009-05-05 13:09 ` Hui Zhu
2009-05-05 18:41 ` Eli Zaretskii
2009-05-06 2:13 ` Hui Zhu
2009-05-06 3:14 ` Eli Zaretskii
2009-05-06 3:35 ` Hui Zhu
2009-05-06 18:28 ` Eli Zaretskii
2009-05-07 2:21 ` Hui Zhu
2009-05-07 3:20 ` Eli Zaretskii
2009-05-11 7:06 ` Hui Zhu
2009-06-09 2:17 ` Hui Zhu [this message]
2009-06-13 22:56 ` Michael Snyder
2009-06-14 9:26 ` Hui Zhu
2009-06-14 17:42 ` Michael Snyder
2009-06-15 8:04 ` Hui Zhu
2009-06-15 17:52 ` Michael Snyder
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=daef60380906081917k3eabe59an2ba2a2983c139d10@mail.gmail.com \
--to=teawater@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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