From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28535 invoked by alias); 3 Dec 2009 02:57:42 -0000 Received: (qmail 28526 invoked by uid 22791); 3 Dec 2009 02:57:41 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f215.google.com (HELO mail-ew0-f215.google.com) (209.85.219.215) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Dec 2009 02:57:30 +0000 Received: by ewy7 with SMTP id 7so1087304ewy.8 for ; Wed, 02 Dec 2009 18:57:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.103.83 with SMTP id j19mr4493770ebo.31.1259809048031; Wed, 02 Dec 2009 18:57:28 -0800 (PST) In-Reply-To: <4B142C54.7070207@vmware.com> References: <5e81cb500911262231g57f693dwc885576172e016e1@mail.gmail.com> <5e81cb500911270711wb99d531i111d064f05ef03b4@mail.gmail.com> <5e81cb500911270742j546062f2jca7441a912ffad87@mail.gmail.com> <4B10154F.7070902@vmware.com> <5e81cb500911271745t1a119520l4944919d2139e8ae@mail.gmail.com> <4B11607C.7000500@vmware.com> <5e81cb500911300539r52e8be5dva54d32c734978021@mail.gmail.com> <4B142C54.7070207@vmware.com> Date: Thu, 03 Dec 2009 02:57:00 -0000 Message-ID: <5e81cb500912021857i3b0d8f42rde841973757b2d48@mail.gmail.com> Subject: Re: System call support in reversible debugging From: Sean Chen To: Michael Snyder Cc: Hui Zhu , "gdb@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-12/txt/msg00017.txt.bz2 On Tue, Dec 1, 2009 at 4:34 AM, Michael Snyder wrote: > Not a black box -- but not a detailed implementation either. > Each system call has a specification -- that's all we need to > understand. =A0The 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. > Sean, this stuff is already implemented and working. > Why don't you have a look at the existing code in > linux-record.c? =A0It sounds like you're more than qualified > to understand it. =A0If you find something that's not working > correctly, please let us know! =A0;-) I am reading the source and the archive of the mailing list. Do you have other systematic documents on this technique? Life becomes better with your help. Thanks. :) --=20 Best Regards, Sean Chen