From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25624 invoked by alias); 26 Oct 2009 07:54:39 -0000 Received: (qmail 25600 invoked by uid 22791); 26 Oct 2009 07:54:38 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from dns.vtab.com (HELO oden.vtab.com) (62.20.90.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 07:54:31 +0000 Received: from oden.vtab.com (oden.vtab.com [127.0.0.1]) by oden.vtab.com (Postfix) with ESMTP id D7A7D26EF24; Mon, 26 Oct 2009 08:54:28 +0100 (CET) Received: from polhem (c83-253-31-27.bredband.comhem.se [83.253.31.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oden.vtab.com (Postfix) with ESMTP id AF81126EEFD; Mon, 26 Oct 2009 08:54:28 +0100 (CET) From: "Jakob Engblom" To: "'Marc Khouzam'" , "'Hui Zhu'" Cc: "'Michael Snyder'" , References: <4ADA4BD8.6080800@vmware.com> In-Reply-To: Subject: RE: [FYI] tutorial for process record and reverse debugging Date: Mon, 26 Oct 2009 07:58:00 -0000 Message-ID: <009c01ca5611$8c520a20$a4f61e60$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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/msg00371.txt.bz2 > 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. /jakob