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: Simics & reverse execution

From: "Jakob Engblom" <jakob at virtutech dot com>
To: "'Pedro Alves'" <pedro at codesourcery dot com>, <gdb at sourceware dot org>
Cc: "'Michael Snyder'" <msnyder at vmware dot com>, "'Hui Zhu'" <teawater at gmail dot com>
Date: Thu, 20 Aug 2009 08:54:31 +0200
Subject: RE: Simics & reverse execution
References: <002001ca1f0e$4c9b74a0$e5d25de0$@com> <010601ca2106$90d41920$b27c4b60$@com> <4A8C5997.1080705@vmware.com> <200908192144.15130.pedro@codesourcery.com>

> > Sounds like a good idea. ?Maybe a 'q' query?
> > "qReverse", maybe?
> 
> Why not use the standard qSupported mechanism?  I think
> we've been over this before.  :-)

You are the experts on this. Tell us what the query is and we will implement it.


I was mostly concerned with any ill effects of reversing to before gdb started.
Looks like the state maintained is sufficiently time-independent that that is
not a problem.

I have no insight into the gdb roadmap, but wasn't there a discussion on adding
time and bookmarks in the execution at some point?  That would be very
worthwhile as an addition, I think.

/jakob

Follow-Ups:
- Re: Simics & reverse execution
  - From: Pedro Alves

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

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