Re: Process record and replay checked in to main trunk

Hui Zhu
2009-05-06T13:34:54Z

Hi Eli,

On Wed, May 6, 2009 at 03:52, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 5 May 2009 21:32:08 +0200 (CEST)
>> From: Mark Kettenis <mark.kettenis@xs4all.nl>
>> CC: teawater@gmail.com, gdb-patches@sourceware.org
>>
>> As far as I know all open source Unix-like operating systems implement systemcalls using int0x80 amd/or syscall.
>
> That still isn't general enough to cover every i386 target, is it?
>

I think it cover most of them.

> Maybe I'm wrong in assuming that OS specifics should be kept out of
> i386-tdep.c.

This just a interface. Any OS that use intx80 and sysenter to do some
special thing (for example system call) will set it.

>
> And I still don't understand why cannot some hypothetical i386 target
> to use the _name_ i386_intx80_record to support sycalls that are
> entered through an interrupt other than 80h.  Hui seemed to say this
> name is reserved for syscalls through Int 80h.
>
> If the name is not special, why not call it i386_syscall_record, for
> example?

Because some os use intx80, others use sysenter. Linux is special.
Linux 2.4 use intx80, 2.6 use sysenter.

Thanks,
Hui