From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] Update documentation on catching a group of related syscalls.
Date: Wed, 12 Nov 2014 02:04:00 -0000 [thread overview]
Message-ID: <87ppctkwcz.fsf@krisman.be> (raw)
In-Reply-To: <83vbmxwfnk.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 02 Nov 2014 21:45:03 +0200")
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
Eli,
Thanks for your review.
>> +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? :)
--
Gabriel Krisman Bertazi
[-- Attachment #2: Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-11-12 2:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 19:36 [PATCH 0/4] Catch syscall groups Gabriel Krisman Bertazi
2014-11-02 19:36 ` [PATCH 2/4] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-11-14 22:55 ` Sergio Durigan Junior
2014-11-02 19:36 ` [PATCH 1/4] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-11-14 22:42 ` Sergio Durigan Junior
2014-11-02 19:37 ` [PATCH 4/4] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2014-11-02 19:45 ` Eli Zaretskii
2014-11-12 2:04 ` Gabriel Krisman Bertazi [this message]
2014-11-12 3:48 ` Eli Zaretskii
2014-11-14 18:52 ` Gabriel Krisman Bertazi
2014-11-14 20:38 ` Eli Zaretskii
2014-11-03 18:38 ` Sergio Durigan Junior
2014-11-02 19:37 ` [PATCH 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2014-11-14 23:00 ` Sergio Durigan Junior
2014-11-20 2:11 ` Gabriel Krisman Bertazi
2014-11-20 3:08 ` Sergio Durigan Junior
2014-11-21 19:05 ` [PATCH v2 1/4] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-11-29 0:19 ` [ping PATCH " Gabriel Krisman Bertazi
2014-12-08 0:09 ` [ping^2 " Gabriel Krisman Bertazi
2014-12-21 15:59 ` [ping^3 " Gabriel Krisman Bertazi
2015-01-12 20:47 ` Doug Evans
2015-01-15 8:03 ` [PATCH " Doug Evans
2015-01-29 4:43 ` Gabriel Krisman Bertazi
2015-01-29 7:42 ` Doug Evans
2014-11-21 19:05 ` [PATCH v2 2/4] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-11-21 21:34 ` Sergio Durigan Junior
2015-01-15 8:12 ` Doug Evans
2014-11-21 19:06 ` [PATCH v2 4/4] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2014-11-21 19:48 ` Eli Zaretskii
2014-11-26 3:58 ` Gabriel Krisman Bertazi
2014-11-21 19:06 ` [PATCH v2 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2015-01-15 8:28 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppctkwcz.fsf@krisman.be \
--to=gabriel@krisman.be \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox