From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2313 invoked by alias); 23 Aug 2009 18:32:19 -0000 Received: (qmail 2304 invoked by uid 22791); 23 Aug 2009 18:32:16 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_BL_SPAMCOP_NET,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 23 Aug 2009 18:32:09 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KOU00G00E29HK00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Sun, 23 Aug 2009 21:31:51 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.180.85]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KOU00EZ4E51U390@a-mtaout22.012.net.il>; Sun, 23 Aug 2009 21:31:50 +0300 (IDT) Date: Sun, 23 Aug 2009 22:48:00 -0000 From: Eli Zaretskii Subject: Re: [RFA/RFC Prec] Add process record skip 6/6 (doc) In-reply-to: To: Hui Zhu Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com Reply-to: Eli Zaretskii Message-id: <8363cefkkp.fsf@gnu.org> References: <837hwzir3w.fsf@gnu.org> 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: 2009-08/txt/msg00372.txt.bz2 > From: Hui Zhu > Date: Sun, 23 Aug 2009 11:33:28 +0800 > Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com > > I make a new patch that have some introduction about record skip entry. > What do you think about it? Thanks. This is much better, but I still don't understand something: > +The record skip entry is a special breakpoint. When the process > +record and replay target start, it will be inserted to the > +begin of a function. Which function is that? The 3 "rec skip" commands you document here don't give the user a way to specify any functions. So how does process record know what function(s) to skip? > When this breakpoint break the inferior and > +@value{GDBN} is in record mode, @value{GDBN} will skip record all > +the execution log of this function's instructions and record the > +change of memory and registers of this function as one instruction. Why is this feature useful? > +Show the status of record skip. Will this produce a list of all rec skip entries, or will it just show the status of the ``current'' record skip (whatever ``current'' may mean in this context)? If it shows a list, how about an example of what this list looks like? Once I understand these issues, I will be able to suggest how to reword this text to be more clear, and also improve the markup. Thanks.