Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Michael Snyder'" <msnyder@vmware.com>
Cc: "'Eli Zaretskii'" <eliz@gnu.org>, 	<glaw@undo-software.com>,
		<gdb-patches@sourceware.org>
Subject: RE: GDB MI Reverse Commands added [2 of 3]
Date: Tue, 01 Sep 2009 06:37:00 -0000	[thread overview]
Message-ID: <025501ca2ace$a9dad180$fd907480$@com> (raw)
In-Reply-To: <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


  reply	other threads:[~2009-09-01  6:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 14:38 Jakob Engblom
2009-08-26 17:38 ` Eli Zaretskii
2009-08-27 13:48   ` Jakob Engblom
2009-08-28 10:05     ` Eli Zaretskii
2009-08-28 10:08   ` Jakob Engblom
2009-08-28 10:49     ` Eli Zaretskii
2009-08-28 13:41       ` Greg Law
2009-08-28 14:28         ` Eli Zaretskii
2009-08-28 17:12           ` Greg Law
2009-08-28 17:34             ` Eli Zaretskii
2009-08-28 18:49               ` Michael Snyder
2009-08-28 21:32                 ` Eli Zaretskii
2009-08-28 23:28                   ` Michael Snyder
2009-08-29  8:12                     ` Eli Zaretskii
2009-08-29 15:19                       ` Eli Zaretskii
2009-08-31 12:14                     ` Jakob Engblom
2009-08-31 13:06                       ` Jakob Engblom
2009-08-31 15:46                         ` Hui Zhu
2009-08-31 16:47                         ` Eli Zaretskii
2009-09-01  6:41                         ` Jakob Engblom
2009-12-15 19:41                         ` Michael Snyder
2009-12-16  8:01                           ` Vladimir Prus
2009-12-16 18:10                             ` Eli Zaretskii
2009-12-16 18:15                           ` Eli Zaretskii
2009-12-16 19:04                             ` Michael Snyder
2009-12-16 20:01                               ` Eli Zaretskii
2009-12-16 20:45                                 ` Vladimir Prus
2009-12-17 20:15                                   ` Eli Zaretskii
2010-02-12 21:36                                     ` Michael Snyder
2009-08-31 17:56                       ` Michael Snyder
2009-09-01  6:37                         ` Jakob Engblom [this message]
2009-08-29  7:37             ` Jakob Engblom
2009-08-28 10:44   ` Jakob Engblom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='025501ca2ace$a9dad180$fd907480$@com' \
    --to=jakob@virtutech.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=glaw@undo-software.com \
    --cc=msnyder@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox