Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, 	"'teawater'" <teawater@gmail.com>
Cc: <msnyder@vmware.com>, 	<gdb-patches@sourceware.org>
Subject: RE: [reverse RFC] Add documentation for process record and replay
Date: Fri, 17 Oct 2008 19:32:00 -0000	[thread overview]
Message-ID: <00cd01c9308f$002aa0a0$007fe1e0$@com> (raw)
In-Reply-To: <uiqrrmt7r.fsf@gnu.org>

> > > signals? crashes? etc.  Are there things that simply cannot be
> > > reproduced exactly, due to fundamental limitations of the replay
> > > target?
> 
> Do you have an opinion about these concerns?

I would like to jump in here and point out that this will depend on the nature
of the target.  Simics, and presumably other full-system simulation solutions,
can replay the entire IO of a machine.  This includes any external IO that is
asynch to the simulator execution (such as network packets and user input).
Between machines in a simulated network of machines, replay is obviously
perfect. 

If you try to do this on a live machine, it is a bit more tricky. 

So this is best left to the underlying mechanism, in my experience.

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
________________________________________________________
 




  parent reply	other threads:[~2008-10-17 19:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 15:01 teawater
2008-10-14 16:34 ` Eli Zaretskii
2008-10-15  5:51   ` teawater
2008-10-15  7:24     ` Eli Zaretskii
2008-10-15  7:34       ` teawater
2008-10-15  8:15         ` Eli Zaretskii
2008-10-15  8:41           ` teawater
2008-10-15  9:33             ` Eli Zaretskii
2008-10-15 18:52       ` Michael Snyder
2008-10-15 19:45         ` Eli Zaretskii
2008-10-16  2:10           ` teawater
2008-10-16  7:02             ` Eli Zaretskii
2008-10-16  7:05               ` teawater
2008-10-16  7:35                 ` teawater
2008-10-16 18:42                   ` Eli Zaretskii
2008-10-17  3:18                     ` teawater
2008-10-17 10:07                       ` Eli Zaretskii
2008-10-17 15:16                         ` teawater
2008-10-17 19:32                         ` Jakob Engblom [this message]
2008-10-17 19:44                           ` Michael Snyder
2008-10-17 19:49                           ` Eli Zaretskii
2008-10-18  1:21                             ` teawater
2008-10-18  1:44                             ` teawater
2008-10-22  2:39                             ` teawater
2008-10-22 19:50                               ` Eli Zaretskii
2008-10-23  3:06                                 ` teawater

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='00cd01c9308f$002aa0a0$007fe1e0$@com' \
    --to=jakob@virtutech.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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