From: pi3orama <pi3orama@gmail.com>
To: Robert Bu <robert.bu@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: ReBranch - a record-replay debugging tool
Date: Mon, 13 Jun 2011 02:03:00 -0000 [thread overview]
Message-ID: <4DF56F5D.2090000@gmail.com> (raw)
In-Reply-To: <BANLkTi=ziszkXzPZE-P2TEewmJrfN3Op0Q@mail.gmail.com>
Yes, you are right.
(P.S:
On the perspective of user processes, all IO interactions are come from
system calls, so for single thread processes, most of the time recording
system calls is enough for data-flow. The only exception I have seen is
vmsplice(): it temporary makes shared memory between 2 processes.)
> Hi,
>
> For data flow, recording syscall is not enough. There may be IO interaction.
> I think your current implementation looks like a PC tracing, replaying tool.
>
> Robert
>
>> From: pi3orama <pi3orama@gmail.com>
>> To: paawan oza <paawan1982@yahoo.com>
>> Date: Fri, 10 Jun 2011 17:34:23 +0800
>> Subject: Re: ReBranch - a record-replay debugging tool
>> In multi-thread situation, nearly all data-flow information is lost
>> because of propagation. However, in single thread situation, signal
>> processing and system call results are all recorded and replayed, all
>> data-flow info can still be restored.
>>
>>> ok got that point.
>>> so in conclusion, any data-flow info which is reponsible for crash may not be
>>> caught by rebranch, or there is a way ?
>>>
>>> Regards,
>>> Oza.
next prev parent reply other threads:[~2011-06-13 2:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 1:57 Robert Bu
2011-06-13 2:03 ` pi3orama [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 16:39 Nan Wang
2011-06-09 19:20 ` paawan oza
[not found] ` <bcaec5215b03b867ea04a5500b35@google.com>
2011-06-10 1:55 ` pi3orama
2011-06-10 8:04 ` paawan oza
2011-06-10 8:15 ` pi3orama
2011-06-10 9:14 ` paawan oza
2011-06-10 9:36 ` pi3orama
2011-06-10 5:51 ` Yao Qi
2011-06-10 6:39 ` pi3orama
[not found] <bcaec5395f2aa367da04a5462782@google.com>
2011-06-09 12:26 ` Pedro Alves
2011-06-09 12:54 ` pi3orama
2011-06-09 14:37 ` Joel Brobecker
2011-06-09 14:51 ` Pedro Alves
[not found] ` <BANLkTi=Mk0-PXb=7m0RZvEt7jegz17JXHw@mail.gmail.com>
2011-06-09 16:11 ` pi3orama
2011-06-09 16:20 ` Pedro Alves
[not found] <1307602807.17016.ezmlm@sourceware.org>
2011-06-09 7:23 ` pi3orama
2011-06-09 9:27 ` Pedro Alves
2011-06-09 10:32 ` paawan oza
2011-06-09 13:05 ` pi3orama
[not found] ` <4DF0A729.4070106@gmail.com>
2011-06-09 11:23 ` Pedro Alves
2011-06-09 12:06 ` pi3orama
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=4DF56F5D.2090000@gmail.com \
--to=pi3orama@gmail.com \
--cc=gdb@sourceware.org \
--cc=robert.bu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).