From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17229 invoked by alias); 5 Nov 2008 14:57:30 -0000 Received: (qmail 17187 invoked by uid 22791); 5 Nov 2008 14:57:29 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Nov 2008 14:56:47 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id E1DD110CE5; Wed, 5 Nov 2008 14:56:45 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id CDE0810814; Wed, 5 Nov 2008 14:56:45 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KxjoL-0006wu-Gw; Wed, 05 Nov 2008 09:56:45 -0500 Date: Wed, 05 Nov 2008 14:57:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org Subject: Re: [PATCH 3/4] 'catch syscall' feature -- XML support part Message-ID: <20081105145645.GB26401@caradoc.them.org> Mail-Followup-To: Eli Zaretskii , sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org References: <1225773086.24532.55.camel@miki> <20081104222225.GA5391@caradoc.them.org> <20081104223544.GD5391@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) 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/msg00080.txt.bz2 On Wed, Nov 05, 2008 at 06:21:36AM +0200, Eli Zaretskii wrote: > What happens if I have a list of syscalls that includes some which are > unsupported by my kernel? What would happen if I ask GDB to trace > those unsupported calls? It will work fine. We trace all system calls (on the only supported implementation, and on the other implementations I'm familiar with). If your application never makes the unsupported system calls, they'll never come up; if it does, they'll be caught (and on exit, return an error, most likely but not always ENOSYS). > In the opposite case (a kernel that supports more syscalls than in the > list), I understand I get an error message if I request the syscall by > name, abut I should be able to request it by the number, right? (This > should be described in the manual, and perhaps also said in the error > message.) That's right. -- Daniel Jacobowitz CodeSourcery