From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6365 invoked by alias); 5 May 2010 02:49:22 -0000 Received: (qmail 6352 invoked by uid 22791); 5 May 2010 02:49:21 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,SARE_MSGID_LONG45 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; Wed, 05 May 2010 02:49:16 +0000 Received: by pvg3 with SMTP id 3so1042602pvg.0 for ; Tue, 04 May 2010 19:49:15 -0700 (PDT) Received: by 10.143.47.6 with SMTP id z6mr1409135wfj.146.1273027755146; Tue, 04 May 2010 19:49:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.4.9 with HTTP; Tue, 4 May 2010 19:48:55 -0700 (PDT) In-Reply-To: References: <83iq78x1yz.fsf@gnu.org> <83k4rjv9n1.fsf@gnu.org> From: Hui Zhu Date: Wed, 05 May 2010 02:49:00 -0000 Message-ID: Subject: Re: [Discussion/Prec] The record speed up plan (Make speed like without prec) To: Eli Zaretskii Cc: gdb@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-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-05/txt/msg00024.txt.bz2 BTW, for the name pre_record. Do you have more better idea? Thanks, Hui On Wed, May 5, 2010 at 09:53, Hui Zhu wrote: > On Wed, May 5, 2010 at 01:50, Eli Zaretskii wrote: >>> From: Hui Zhu >>> Date: Tue, 4 May 2010 10:44:17 +0800 >>> Cc: gdb@sourceware.org, msnyder@vmware.com >>> >>> On Sat, May 1, 2010 at 01:52, Eli Zaretskii wrote: >>> > >>> > > From: Hui Zhu >>> > > Date: Fri, 30 Apr 2010 21:23:20 +0800 >>> > > Cc: Michael Snyder >>> > > >>> > > But lucky for us that insns exec rules we know. =A0So most of insns >>> > > (There a some special, I will talk it later), if we have the a >>> > > inferior value(memory and reg), we can get the each value of next >>> > > insn. >>> > >>> > I don't see how you can do that, unless you first read the entire >>> > memory of the inferior. =A0Otherwise, when an instruction references >>> > some address, how do you know what value is stored at that address? >>> > >>> >>> You mean before or after the insn? >> >> Before, of course. >> >>> For the before, we do something like fork to record all of them. >> >> "Record" where? in GDB's memory? > > fork a new process.... > >> >>> > Also, what do you do with features such as shared memory, where the >>> > value at a given address can change beyond control of the current >>> > inferior, and change the result of some instruction which references >>> > that address? >>> >>> Agree, but we can give up of them like we give up the released memory n= ow. >> >> IMHO, that'd be giving up too much. =A0Prec is supposed to be a >> general-purpose tool, so designing it along an idea that has severe >> limitations from the get-go is not something I'd recommend. >> > > About this issue: > 1. We have a switch for pre-record to close it. =A0The people can choice > to open or close it. > 2. The increase need step by step. =A0I am not a superman. =A0:) > We will find good way to handle every limit like x86 segment reg. > > Thanks, > Hui >