From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20009 invoked by alias); 4 Dec 2009 15:40:33 -0000 Received: (qmail 19985 invoked by uid 22791); 4 Dec 2009 15:40:29 -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-f209.google.com (HELO mail-ew0-f209.google.com) (209.85.219.209) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Dec 2009 15:39:45 +0000 Received: by ewy1 with SMTP id 1so156410ewy.14 for ; Fri, 04 Dec 2009 07:39:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.104.78 with SMTP id n14mr3361001ebo.22.1259941183036; Fri, 04 Dec 2009 07:39:43 -0800 (PST) In-Reply-To: <00a101ca73f7$13fe26e0$3bfa74a0$@com> References: <5e81cb500911262231g57f693dwc885576172e016e1@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> <5e81cb500912021857i3b0d8f42rde841973757b2d48@mail.gmail.com> <00a101ca73f7$13fe26e0$3bfa74a0$@com> Date: Fri, 04 Dec 2009 15:40:00 -0000 Message-ID: <5e81cb500912040739r1bef581ew6fc598bfaf024adc@mail.gmail.com> Subject: Re: System call support in reversible debugging From: Sean Chen To: Jakob Engblom Cc: Michael Snyder , Hui Zhu , gdb@sourceware.org Content-Type: text/plain; charset=windows-1252 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/msg00028.txt.bz2 On Thu, Dec 3, 2009 at 5:00 PM, Jakob Engblom 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. > > I guess these have to be the header files specifying the function call > prototypes? > > Or is something else also done for precord? > > /jakob > > I searched sys_open in the whole Linux kernel, and I didn=92t find such information. Thanks all the same. --=20 Best Regards, Sean Chen