This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: GDB MI Reverse Commands added [2 of 3]
- From: "Jakob Engblom" <jakob at virtutech dot com>
- To: "'Michael Snyder'" <msnyder at vmware dot com>
- Cc: "'Eli Zaretskii'" <eliz at gnu dot org>, <glaw at undo-software dot com>, <gdb-patches at sourceware dot org>
- Date: Tue, 1 Sep 2009 08:37:12 +0200
- Subject: RE: GDB MI Reverse Commands added [2 of 3]
- 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> <83ljl3c16f.fsf@gnu.org> <4A981551.4060504@vmware.com> <83k50nbrja.fsf@gnu.org> <4A9865A5.1020703@vmware.com> <00d201ca2a33$454aa920$cfdffb60$@com> <4A9C0E58.6080500@vmware.com>
> > I.e., in process record, do you have to record everything first and then
debug
> > it?
>
> You can record everything first and then debug it.
> You can also debug it while you're recording it.
> I *think* (and this is just based on my experience,
> Hui may be able to say something different) that the
> recording mode is "over" as soon as you go into
> replay mode, and so that represents the "end" of
> your recording.
OK. Simics does not have this behavior, if you hit the "last known time" as we
call it, the simulation will just continue forward, accumulating reversible
state. But I guess that is not an issue, as gdb has no idea of these limits, it
is all up to the remote backend.
/jakob