This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: reverse for GDB/MI
- From: "Jakob Engblom" <jakob at virtutech dot com>
- To: <gdb-patches at sources dot redhat dot com>
- Date: Sat, 3 Jan 2009 19:08:52 +0100
- Subject: RE: reverse for GDB/MI
- References: <49463870.6080302@virtutech.com> <gib8ll$dus$1@ger.gmane.org> <494A0A9C.6020809@virtutech.com> <gid1vj$irm$1@ger.gmane.org> <494B5A82.4020004@virtutech.com> <494BF080.9060009@vmware.com> <6D19CA8D71C89C43A057926FE0D4ADAA06B06B04@ecamlmw720.eamcs.ericsson.se>
> Hi,
>
> It was pointed out to me that people who have been doing reversible
> debug for a while seems to
> have specific commands for reverse debugging and they do have a command
> for "go to time point P".
> For example http://www.undo-software.com/undodb_man.html:
>
> bgoton <number>
> Move forwards or backwards to the specified time, in simulated
> nanoseconds.
> bgoton +<number> | -<number>
> Step forward/backward the specified number of simulated nanoseconds.
Simics has it to, in some different ways:
skip-to <bookmark>
reverse n time units
continue n time units
I think this is a good example of the kind of new commands and abilities that
come with having a reverse ability in the first place, like Marc said.
And as the later discussion evolved, it would be jolly nice to have an idea of
time in gdb. I think that is needed anyway to handle multicore, multiprocessor,
and multithreaded debug: when things happen in disparate locations under the
control of a single debugger quickly gets very interesting...
Best regards,
/jakob
_______________________________________________________
Jakob Engblom, PhD, Technical Marketing Manager
Virtutech Direct: +46 8 690 07 47
Drottningholmsvägen 14 Mobile: +46 709 242 646
11243 Stockholm Web: www.virtutech.com
Sweden
________________________________________________________