This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 4/4] Update documentation on catching a group of related syscalls.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Gabriel Krisman Bertazi <gabriel at krisman dot be>
- Cc: gdb-patches at sourceware dot org, gabriel at krisman dot be
- Date: Sun, 02 Nov 2014 21:45:03 +0200
- Subject: Re: [PATCH 4/4] Update documentation on catching a group of related syscalls.
- Authentication-results: sourceware.org; auth=none
- References: <1414956944-8856-1-git-send-email-gabriel at krisman dot be> <1414956944-8856-5-git-send-email-gabriel at krisman dot be>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Gabriel Krisman Bertazi <gabriel@krisman.be>
> Cc: Gabriel Krisman Bertazi <gabriel@krisman.be>
> Date: Sun, 2 Nov 2014 17:35:44 -0200
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 649c29e..edea1ff 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
This part is OK.
> @item syscall
> -@itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @dots{}
> +@itemx syscall @r{[}@var{name} @r{|} @var{number} @r{|} @var{group:groupname} @r{|} @var{g:groupname}@r{]} @dots{}
Only "groupname" should be in @var, the "g:" and "group:" prefixes are
literal strings, so they should be in @r{}, like the brackets.
> +You may specify a group of related syscalls to be caught at once
> +using the @code{group:} syntax (@code{g:} is a shorter equivalent.).
> +For instance, on some platforms GDB allows you to catch all network
^^^
"@value{GDBN}"
> +related syscalls, by passing the argument @code{group:network} to
> +@code{catch syscall}.
How does one know which groups, if any, exist?
Thanks.