From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] 'catch syscall' feature -- XML support part
Date: Tue, 04 Nov 2008 22:27:00 -0000 [thread overview]
Message-ID: <utzant9gi.fsf@gnu.org> (raw)
In-Reply-To: <20081104222225.GA5391@caradoc.them.org>
> Date: Tue, 4 Nov 2008 17:22:25 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= <sergiodj@linux.vnet.ibm.com>,
> gdb-patches@sourceware.org
>
> > Is the list of syscalls and their numbers kernel version dependent?
> > If it is, how will we go about maintaining these files?
>
> Fortunately, it is not. There are some exceptions in vendor-provided
> kernels, but there is a very strong incentive to not reuse or adjust
> syscall numbers.
Does this mean we can be sure no new syscalls will be added to the
list, ever?
next prev parent reply other threads:[~2008-11-04 22:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 4:32 Sérgio Durigan Júnior
2008-11-04 13:36 ` Mark Kettenis
2008-11-04 13:47 ` Daniel Jacobowitz
2008-11-04 15:05 ` Sérgio Durigan Júnior
2008-11-04 15:13 ` Daniel Jacobowitz
2008-11-04 15:18 ` Sérgio Durigan Júnior
2008-11-04 15:06 ` Sérgio Durigan Júnior
2008-11-08 19:06 ` Mark Kettenis
2008-11-04 18:41 ` Tom Tromey
2008-11-07 3:46 ` Sérgio Durigan Júnior
2008-11-07 18:24 ` Tom Tromey
2008-11-04 21:20 ` Eli Zaretskii
2008-11-04 22:23 ` Daniel Jacobowitz
2008-11-04 22:27 ` Eli Zaretskii [this message]
2008-11-04 22:36 ` Daniel Jacobowitz
2008-11-05 1:02 ` Sérgio Durigan Júnior
2008-11-05 4:22 ` Eli Zaretskii
2008-11-05 14:57 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=utzant9gi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox