From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29025 invoked by alias); 1 Sep 2009 06:37:36 -0000 Received: (qmail 28877 invoked by uid 22791); 1 Sep 2009 06:37:35 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from vtab.com (HELO oden.vtab.com) (62.20.90.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Sep 2009 06:37:22 +0000 Received: from oden.vtab.com (oden.vtab.com [127.0.0.1]) by oden.vtab.com (Postfix) with ESMTP id 53AC526EF6A; Tue, 1 Sep 2009 08:37:20 +0200 (CEST) Received: from polhem (95.209.37.191.bredband.tre.se [95.209.37.191]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oden.vtab.com (Postfix) with ESMTP id 8849826EF3A; Tue, 1 Sep 2009 08:37:19 +0200 (CEST) From: "Jakob Engblom" To: "'Michael Snyder'" Cc: "'Eli Zaretskii'" , , References: <00cf01ca265a$d4110dc0$7c332940$@com> <83tyzucw8p.fsf@gnu.org> <002b01ca27c7$1316d8c0$39448a40$@com> <833a7ccj52.fsf@gnu.org> <4A97BA98.4010105@undo-software.com> <83y6p4aweu.fsf@gnu.org> <4A980D06.40002@undo-software.com> <83ljl3c16f.fsf@gnu.org> <4A981551.4060504@vmware.com> <83k50nbrja.fsf@gnu.org> <4A9865A5.1020703@vmware.com> <00d201ca2a33$454aa920$cfdffb60$@com> <4A9C0E58.6080500@vmware.com> In-Reply-To: <4A9C0E58.6080500@vmware.com> Subject: RE: GDB MI Reverse Commands added [2 of 3] Date: Tue, 01 Sep 2009 06:37:00 -0000 Message-ID: <025501ca2ace$a9dad180$fd907480$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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-09/txt/msg00011.txt.bz2 > > I.e., in process record, do you have to record everything first and then debug > > it? > > You can record everything first and then debug it. > You can also debug it while you're recording it. > I *think* (and this is just based on my experience, > Hui may be able to say something different) that the > recording mode is "over" as soon as you go into > replay mode, and so that represents the "end" of > your recording. OK. Simics does not have this behavior, if you hit the "last known time" as we call it, the simulation will just continue forward, accumulating reversible state. But I guess that is not an issue, as gdb has no idea of these limits, it is all up to the remote backend. /jakob