From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6523 invoked by alias); 4 Nov 2008 22:12:24 -0000 Received: (qmail 6499 invoked by uid 22791); 4 Nov 2008 22:12:23 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 04 Nov 2008 22:11:37 +0000 Received: from d24relay01.br.ibm.com (unknown [9.8.31.16]) by igw2.br.ibm.com (Postfix) with ESMTP id 8EF5C17F471 for ; Tue, 4 Nov 2008 20:10:07 -0200 (BRDT) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by d24relay01.br.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mA4MBDB23186810 for ; Tue, 4 Nov 2008 19:11:13 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mA4MBYoN022191 for ; Tue, 4 Nov 2008 20:11:34 -0200 Received: from [9.8.11.66] ([9.8.11.66]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mA4MBWkB022126; Tue, 4 Nov 2008 20:11:33 -0200 Subject: Re: [PATCH 1/4] 'catch syscall' feature -- Architecture-independent part From: Thiago Jung Bauermann To: Eli Zaretskii Cc: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= , gdb-patches@sourceware.org In-Reply-To: References: <1225773079.24532.52.camel@miki> Content-Type: text/plain; charset=utf-8 Date: Tue, 04 Nov 2008 22:12:00 -0000 Message-Id: <1225836687.20764.21.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 8bit 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/msg00057.txt.bz2 El mar, 04-11-2008 a las 23:12 +0200, Eli Zaretskii escribió: > Who said that a syscall is necessarily defined by some number? I assumed every OS used numbers to define syscalls ... > More generally, let's say I'd like to implement support for this on > Windows -- how would I need to go about it? ... but from what you are saying it seems that in Windows it's different. What's the proper datatype to represent a syscall there? > > + /* Checking if the user provided a syscall name or a number. */ > > + if (isdigit (cur_name[0])) > > Is the assumption that no name will ever begin with a digit > universally valid? Syscall names need to be valid function names in at least the most common programming languages. I'm far from being a specialist, but isn't it a very common (or universal?) restriction that function names have to start with a non-digit character? -- []'s Thiago Jung Bauermann IBM Linux Technology Center