From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19578 invoked by alias); 26 Oct 2009 15:53:07 -0000 Received: (qmail 19566 invoked by uid 22791); 26 Oct 2009 15:53:06 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 15:52:59 +0000 Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 8008243023; Mon, 26 Oct 2009 08:52:58 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost3.vmware.com (Postfix) with ESMTP id 730A3CD9E2; Mon, 26 Oct 2009 08:52:58 -0700 (PDT) Message-ID: <4AE5C41F.6000000@vmware.com> Date: Mon, 26 Oct 2009 19:10:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Jakob Engblom CC: 'Marc Khouzam' , 'Hui Zhu' , "gdb@sourceware.org" Subject: Re: [FYI] tutorial for process record and reverse debugging References: <4ADA4BD8.6080800@vmware.com> <009c01ca5611$8c520a20$a4f61e60$@com> In-Reply-To: <009c01ca5611$8c520a20$a4f61e60$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-10/txt/msg00378.txt.bz2 Jakob Engblom wrote: >> If going straight to the end of the recording log is a valuable >> feature, I was thinking it may deserve its own command. >> >> Ultimately, I'm hoping that with such a command, we can then see >> if we can have PRecord directly jump from recorded execution >> to live execution without stopping. > > Note that we had a discussion a while ago about adding a general "go to point in > time in recording/reverse execution history" command, which would kind of solve > this as a special case (provided you can find the "last" time). We can already > do this in Simics, but there is no support in the gdb-serial protocol or the gdb > CLI or MI to access the function. The undodb people had the same issue. What would you think of "qBookmark" to request a bookmark id, and "QBookmark:id" to "set" the bookmark (that is, to go back to that machine state)?