Re: [RFC 3/3] catch syscall -- try 6 -- Build system, testcase and documentation

[Eli Zaretskii <eliz@gnu.org>]

> From: =?iso-8859-1?q?S=E9rgio_Durigan_J=FAnior?= <sergiodj@linux.vnet.ibm.com>
> 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.