From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-35243-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 2655 invoked by alias); 17 Aug 2009 11:55:13 -0000
Received: (qmail 2647 invoked by uid 22791); 17 Aug 2009 11:55:12 -0000
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Aug 2009 11:55:04 +0000
Received: (qmail 23649 invoked from network); 17 Aug 2009 11:55:02 -0000
Received: from unknown (HELO orlando.local) (pedro@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 17 Aug 2009 11:55:02 -0000
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: gdb reverse execution: how to actually run tests for it?
Date: Mon, 17 Aug 2009 15:31:00 -0000
User-Agent: KMail/1.9.10
Cc: "Jakob Engblom" <jakob@virtutech.com>
References: <002001ca1f0e$4c9b74a0$e5d25de0$@com> <002101ca1f2e$746e1ad0$5d4a5070$@com> <200908171251.07179.pedro@codesourcery.com>
In-Reply-To: <200908171251.07179.pedro@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200908171255.28644.pedro@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-08/txt/msg00142.txt.bz2

On Monday 17 August 2009 12:51:06, Pedro Alves wrote:
> In any case, for the cases a board file is needed for testing
> reverse, it would be nice to have that explained in the
> wiki (or somewhere else).

I should add that it is a shame that the remote targets
don't report support for reverse until GDB tries it first...

How bad is the failure mode in the reverse tests if the target
does not support reverse at all?  Can't we try a simple
probing-for-support reverse test and if that fails skip the
rest of the reverse tests?  That would likely get rid of all
the current needs for a hacked board file.

-- 
Pedro Alves