From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-66321-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 11978 invoked by alias); 28 Aug 2009 17:12:45 -0000
Received: (qmail 11964 invoked by uid 22791); 28 Aug 2009 17:12:44 -0000
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 28 Aug 2009 17:12:38 +0000
Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KP300500JL34W00@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Fri, 28 Aug 2009 20:12:35 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.228.144.38]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KP300JKEJSY2J60@i-mtaout7.012.net.il>; Fri, 28 Aug 2009 20:12:35 +0300 (IDT)
Date: Fri, 28 Aug 2009 17:34:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: GDB MI Reverse Commands added [2 of 3]
In-reply-to: <4A980D06.40002@undo-software.com>
To: Greg Law <glaw@undo-software.com>
Cc: jakob@virtutech.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83ljl3c16f.fsf@gnu.org>
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>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-08/txt/msg00520.txt.bz2

> Date: Fri, 28 Aug 2009 17:59:50 +0100
> From: Greg Law <glaw@undo-software.com>
> CC: jakob@virtutech.com, gdb-patches@sourceware.org
> 
> But I'm struggling to think of a plausible way in which 
> a target could provide reverse debugging without some kind of log.

Don't we have already some kind of that implemented by forking the
inferior several times, and then switching to the appropriate fork
when the user wants to go backwards?

Anyway, a target could conceivably provide reverse execution without
any need for GDB to do that for it.  I don't think the manual should
be too tied to what we currently have, because then it would be a pain
to maintain.