From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14605 invoked by alias); 11 Sep 2009 07:51:37 -0000 Received: (qmail 14597 invoked by uid 22791); 11 Sep 2009 07:51:36 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL 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.43rc1) with ESMTP; Fri, 11 Sep 2009 07:51:30 +0000 Received: from conversion-daemon.i_mtaout5.012.net.il by i_mtaout5.012.net.il (HyperSendmail v2004.12) id <0KPS00000R3DC800@i_mtaout5.012.net.il> for gdb-patches@sourceware.org; Fri, 11 Sep 2009 10:51:26 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.50.163]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KPS00MYOR5Q8MJ0@i_mtaout5.012.net.il>; Fri, 11 Sep 2009 10:51:26 +0300 (IDT) Date: Fri, 11 Sep 2009 07:51:00 -0000 From: Eli Zaretskii Subject: Re: [RFC 3/3] catch syscall -- try 6 -- Build system, testcase and documentation In-reply-to: <200909101940.29528.sergiodj@linux.vnet.ibm.com> To: =?iso-8859-1?q?S=E9rgio_Durigan_J=FAnior?= Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83vdjp2a5t.fsf@gnu.org> References: <200909041600.53576.sergiodj@linux.vnet.ibm.com> <83my594zgu.fsf@gnu.org> <200909101940.29528.sergiodj@linux.vnet.ibm.com> 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: 2009-09/txt/msg00306.txt.bz2 > From: =?iso-8859-1?q?S=E9rgio_Durigan_J=FAnior?= > Date: Thu, 10 Sep 2009 19:40:29 -0300 > Cc: gdb-patches@sourceware.org > > --- a/gdb/NEWS > +++ b/gdb/NEWS > @@ -3,6 +3,18 @@ > > *** Changes since GDB 6.8 > > +* GDB now has the new command `catch syscall'. > + > + catch syscall [NAME(S) | NUMBER(S)] > + Catch system calls. Arguments, which should be names of system > + calls or their numbers, mean catch only those syscalls. Without > + arguments, every syscall will be caught. When the inferior issues > + any of the specified syscalls, GDB will stop and announce the system > + call, both when it is called and when its call returns. This > + feature is currently available with a native GDB running on the > + Linux Kernel, under the following architectures: x86, x86_64, > + PowerPC and PowerPC64. > + > * GDB now has an interface for JIT compilation. Applications that > dynamically generate code can create symbol files in memory and register > them with GDB. For users, the feature should work transparently, and > @@ -234,6 +246,10 @@ powerpc-linux or powerpc64-linux and the spu-elf targets, using the > > * New commands (for set/show, see "New options" below) > > +catch syscall [NAME(S) | NUMBER(S)] > + Catch system calls. Arguments should be names of system calls or their > + numbers. Without arguments, every system call will be caught. > + Sorry, I obviously didn't make myself clear. I didn't mean to have 2 places mentioning this. I meant to have only one description, the first one above, but to put it in the "New commands" section, where you put the second one. Thanks.