From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24514 invoked by alias); 4 Dec 2009 15:46:10 -0000 Received: (qmail 24500 invoked by uid 22791); 4 Dec 2009 15:46:07 -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:46:01 +0000 Received: by ewy1 with SMTP id 1so163881ewy.14 for ; Fri, 04 Dec 2009 07:45:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.102.72 with SMTP id f8mr3373628ebo.26.1259941556165; Fri, 04 Dec 2009 07:45:56 -0800 (PST) In-Reply-To: <4B17EE0D.6010702@vmware.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> <4B17EE0D.6010702@vmware.com> Date: Fri, 04 Dec 2009 15:46:00 -0000 Message-ID: <5e81cb500912040745t6ffc4ebfy7ae917e3be724305@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=UTF-8 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/msg00029.txt.bz2 On Fri, Dec 4, 2009 at 12:57 AM, Michael Snyder wrote: > Sean Chen wrote: >> >> On Tue, Dec 1, 2009 at 4:34 AM, Michael Snyder wrot= e: >>> >>> Not a black box -- but not a detailed implementation either. >>> Each system call has a specification -- that's all we need to >>> understand. =C2=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? =C2=A0It sounds like you're more than qualified >>> to understand it. =C2=A0If you find something that's not working >>> correctly, please let us know! =C2=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. :) > > Teawater implemented them, I am only reverse-engineering > them, like you. =C2=A0Man pages are helpful. =C2=A0 ;-) > > Man pages just tell how to use it. It won=E2=80=99t tell why use it. =EF=81= =8A Hui, Could you help with this? Thanks in advance. --=20 Best Regards, Sean Chen