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
- Date: Wed, 12 Nov 2014 05:47:58 +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> <83vbmxwfnk dot fsf at gnu dot org> <87ppctkwcz dot fsf at krisman dot be>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Gabriel Krisman Bertazi <gabriel@krisman.be>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 12 Nov 2014 00:04:28 -0200
>
> >> +related syscalls, by passing the argument @code{group:network} to
> >> +@code{catch syscall}.
> >
> > How does one know which groups, if any, exist?
> >
>
> Indeed, as I said in part 0, I don't provide any way to list which group
> exists, other than the usual word completion. The reason is that catch
> syscall does not provide a way to list system calls and we couldn't
> agree on the right syntax for this feature on the RFC I sent earlier to
> this list.
>
> Maybe I could rewrite this part of the documentation to suggest
> something like "Tab is your friend". WDYT? :)
Yes, saying that TAB-completion (including M-TAB) can be used to see
the list of groups is fine with me.
Thanks.