From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21127 invoked by alias); 20 Jun 2010 06:02:05 -0000 Received: (qmail 21119 invoked by uid 22791); 20 Jun 2010 06:02:04 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-pv0-f169.google.com (HELO mail-pv0-f169.google.com) (74.125.83.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 20 Jun 2010 06:01:59 +0000 Received: by pvg16 with SMTP id 16so2036682pvg.0 for ; Sat, 19 Jun 2010 23:01:58 -0700 (PDT) Received: by 10.142.67.34 with SMTP id p34mr2231967wfa.335.1277013718223; Sat, 19 Jun 2010 23:01:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.32.8 with HTTP; Sat, 19 Jun 2010 23:01:38 -0700 (PDT) In-Reply-To: <83d3voiyjv.fsf@gnu.org> References: <83d3voiyjv.fsf@gnu.org> From: Hui Zhu Date: Sun, 20 Jun 2010 06:02:00 -0000 Message-ID: Subject: Re: [PATCH] prec: add a switch for memory doesn't record query To: Eli Zaretskii Cc: gdb-patches@sourceware.org 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: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-06/txt/msg00433.txt.bz2 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 wrote: >> From: Hui Zhu >> Date: Fri, 18 Jun 2010 12:59:49 +0800 >> >> Some words in the doc is not very well. =A0Did some small change. > > Thanks. > >> +Control the behavior when PREC cannot record memory change of next >> +instruction. =A0If 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. =A0It can handle it with itself. > > This is too mysterious. =A0I think we should have at least some > explanation of what this auto handling does. =A0Otherwise, the reader > will not be able to decide whether to set this on or not. > >