This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb reverse execution: how to actually run tests for it?

From: Pedro Alves <pedro at codesourcery dot com>
To: gdb at sourceware dot org
Cc: "Jakob Engblom" <jakob at virtutech dot com>
Date: Mon, 17 Aug 2009 12:55:28 +0100
Subject: Re: gdb reverse execution: how to actually run tests for it?
References: <002001ca1f0e$4c9b74a0$e5d25de0$@com> <002101ca1f2e$746e1ad0$5d4a5070$@com> <200908171251.07179.pedro@codesourcery.com>

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

Follow-Ups:
- Re: gdb reverse execution: how to actually run tests for it?
  - From: Hui Zhu
- RE: gdb reverse execution: how to actually run tests for it?
  - From: Jakob Engblom

References:
- gdb reverse execution: how to actually run tests for it?
  - From: Jakob Engblom
- RE: gdb reverse execution: how to actually run tests for it?
  - From: Jakob Engblom
- Re: gdb reverse execution: how to actually run tests for it?
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]