Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Sean Chen'" <sean.chen1234@gmail.com>,
		"'Michael Snyder'" <msnyder@vmware.com>
Cc: "'Hui Zhu'" <teawater@gmail.com>, 	<gdb@sourceware.org>
Subject: RE: System call support in reversible debugging
Date: Thu, 03 Dec 2009 09:00:00 -0000	[thread overview]
Message-ID: <00a101ca73f7$13fe26e0$3bfa74a0$@com> (raw)
In-Reply-To: <5e81cb500912021857i3b0d8f42rde841973757b2d48@mail.gmail.com>

> > Not a black box -- but not a detailed implementation either.
> > Each system call has a specification -- that's all we need to
> > understand.  The specification tells what user-visible external
> > side effects can be expected (eg. this buffer will be filled).
> > Changes that are internal to the kernel do not concern us.
> 
> Thanks. I understand your concern. Does Linux kernel provide such an
> official specification? If so, could you throw me a hint on where to
> get it? Since we have all of the side effects, recording the system
> calls are feasible and trustable.

I guess these have to be the header files specifying the function call
prototypes? 

Or is something else also done for precord?

/jakob


  reply	other threads:[~2009-12-03  9:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27 15:11 Sean Chen
2009-11-27 15:42 ` Hui Zhu
2009-11-27 18:11   ` Sean Chen
2009-11-28  1:45     ` Hui Zhu
2009-11-28 17:44       ` Sean Chen
2009-11-29  2:24         ` Michael Snyder
2009-11-29  2:24           ` Sean Chen
2009-11-30 12:27             ` Michael Snyder
2009-11-30 16:03               ` Hui Zhu
2009-11-30 16:29                 ` Sean Chen
2009-12-01 11:32                   ` Jakob Engblom
2009-12-01 20:21                     ` Greg Law
2009-12-02 17:16                       ` Jakob Engblom
2009-12-03  3:05                         ` Sean Chen
     [not found]                   ` <4B142C54.7070207@vmware.com>
2009-12-03  2:57                     ` Sean Chen
2009-12-03  9:00                       ` Jakob Engblom [this message]
2009-12-04 15:40                         ` Sean Chen
2009-12-03 16:57                       ` Michael Snyder
2009-12-04 15:46                         ` Sean Chen

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='00a101ca73f7$13fe26e0$3bfa74a0$@com' \
    --to=jakob@virtutech.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=sean.chen1234@gmail.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