This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: System call support in reversible debugging
- From: Sean Chen <sean dot chen1234 at gmail dot com>
- To: Jakob Engblom <jakob at virtutech dot com>
- Cc: Michael Snyder <msnyder at vmware dot com>, Hui Zhu <teawater at gmail dot com>, gdb at sourceware dot org
- Date: Fri, 4 Dec 2009 23:39:42 +0800
- Subject: Re: System call support in reversible debugging
- References: <5e81cb500911262231g57f693dwc885576172e016e1@mail.gmail.com> <5e81cb500911270742j546062f2jca7441a912ffad87@mail.gmail.com> <4B10154F.7070902@vmware.com> <5e81cb500911271745t1a119520l4944919d2139e8ae@mail.gmail.com> <4B11607C.7000500@vmware.com> <daef60380911300427p20b2e9bege4087bbcd18bc82a@mail.gmail.com> <5e81cb500911300539r52e8be5dva54d32c734978021@mail.gmail.com> <4B142C54.7070207@vmware.com> <5e81cb500912021857i3b0d8f42rde841973757b2d48@mail.gmail.com> <00a101ca73f7$13fe26e0$3bfa74a0$@com>
On Thu, Dec 3, 2009 at 5:00 PM, Jakob Engblom <jakob@virtutech.com> wrote:
>> > 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
>
>
I searched sys_open in the whole Linux kernel, and I didn’t find such
information. Thanks all the same.
--
Best Regards,
Sean Chen