From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-63527-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 12578 invoked by alias); 5 May 2009 18:41:04 -0000
Received: (qmail 12569 invoked by uid 22791); 5 May 2009 18:41:03 -0000
X-SWARE-Spam-Status: No, hits=0.4 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_JMF_BL,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout4.012.net.il (HELO mtaout3.012.net.il) (84.95.2.10)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 May 2009 18:40:55 +0000
Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KJ600200P7OM300@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Tue, 05 May 2009 21:40:52 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.127.230.216]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KJ6005ZJP839EX0@i_mtaout3.012.net.il>; Tue, 05 May 2009 21:40:52 +0300 (IDT)
Date: Tue, 05 May 2009 18:41:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [Precord RFA/RFC] Check Linux sys_brk release memory in process	record and replay.
In-reply-to: <daef60380905050607yc499e39n34ac56108225f6ec@mail.gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org, msnyder@vmware.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83d4ane6kb.fsf@gnu.org>
References: <daef60380905050607yc499e39n34ac56108225f6ec@mail.gmail.com>
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/msg00090.txt.bz2

> Date: Tue, 5 May 2009 21:07:13 +0800
> From: Hui Zhu <teawater@gmail.com>
> Cc: Michael Snyder <msnyder@vmware.com>
> 
> 15		sbrk (-10);
> (gdb)
> The next instruction is syscall brk.  It will release the memory that
> will cause process record target get error.  Do you want to stop the
> inferior?([y] or n)

Does every sbrk call with a negative argument cause an error in
process record target?  What is the reason for that error?

I'm asking because the message wording sounds very threatening.  It
probably needs rephrasing, but I need to understand the reasons better
to suggest how.

> 	* gdbarch.sh (process_record_reset): This interface point to
> 	the function that reset the architecture process record and
> 	replay.

I think "reset" is not the best name for this.  How about
"initialize"?