From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5673 invoked by alias); 4 Nov 2008 22:27:03 -0000 Received: (qmail 5629 invoked by uid 22791); 4 Nov 2008 22:27:03 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 04 Nov 2008 22:26:21 +0000 Received: from HOME-C4E4A596F7 ([77.126.241.172]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K9T00AAHYD91AT1@i_mtaout5.012.net.il> for gdb-patches@sourceware.org; Wed, 05 Nov 2008 00:27:11 +0200 (IST) Date: Tue, 04 Nov 2008 22:27:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 3/4] 'catch syscall' feature -- XML support part In-reply-to: <20081104222225.GA5391@caradoc.them.org> X-012-Sender: halo1@inter.net.il To: Daniel Jacobowitz Cc: sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <1225773086.24532.55.camel@miki> <20081104222225.GA5391@caradoc.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00061.txt.bz2 > Date: Tue, 4 Nov 2008 17:22:25 -0500 > From: Daniel Jacobowitz > Cc: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= , > 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?