From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-63636-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 3581 invoked by alias); 11 May 2009 07:06:58 -0000
Received: (qmail 3570 invoked by uid 22791); 11 May 2009 07:06:56 -0000
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from ti-out-0910.google.com (HELO ti-out-0910.google.com) (209.85.142.188)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 May 2009 07:06:48 +0000
Received: by ti-out-0910.google.com with SMTP id a1so233841tib.12         for <gdb-patches@sourceware.org>; Mon, 11 May 2009 00:06:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.110.69.5 with SMTP id r5mr439620tia.22.1242025605168; Mon, 11  	May 2009 00:06:45 -0700 (PDT)
In-Reply-To: <83k54td2el.fsf@gnu.org>
References: <daef60380905050607yc499e39n34ac56108225f6ec@mail.gmail.com> 	 <83d4ane6kb.fsf@gnu.org> 	 <daef60380905051913q7579eed8pe8b514e72145859c@mail.gmail.com> 	 <833abiexcc.fsf@gnu.org> 	 <daef60380905052035v2758da1ak27fabfd902dff32d@mail.gmail.com> 	 <83tz3ycchv.fsf@gnu.org> 	 <daef60380905061921k7ced158eu2a74bab604a700e1@mail.gmail.com> 	 <83k54td2el.fsf@gnu.org>
Date: Mon, 11 May 2009 07:06:00 -0000
Message-ID: <daef60380905110006gaa1ac38r870f6be455a402fc@mail.gmail.com>
Subject: Re: [Precord RFA/RFC] Check Linux sys_brk release memory in process  	record and replay.
From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, msnyder@vmware.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-05/txt/msg00199.txt.bz2

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. =A0Is this the problem
>> > you are talking about? =A0If 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. =A0The user just needs to be notified, when
>> > she tries that, that she cannot reverse-replay the log past this
>> > point. =A0If 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. =A0I think
>> let user choice continue or stop is better.
>
> Well, what do others think?
>