From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: gdb-patches@sourceware.org
Cc: Gabriel Krisman Bertazi <gabriel@krisman.be>
Subject: [PATCH 4/4] Update documentation on catching a group of related syscalls.
Date: Sun, 02 Nov 2014 19:37:00 -0000 [thread overview]
Message-ID: <1414956944-8856-5-git-send-email-gabriel@krisman.be> (raw)
In-Reply-To: <1414956944-8856-1-git-send-email-gabriel@krisman.be>
gdb/
* breakpoint.c (_initialize_breakpoint): Update catch syscall
command documentation.
* NEWS: Include section about catching groups of syscalls.
gdb/doc/
* gdb.texinfo (Set Catchpoints): Add 'group' argument to catch
syscall.
---
gdb/NEWS | 5 +++++
gdb/breakpoint.c | 10 +++++-----
gdb/doc/gdb.texinfo | 8 +++++++-
3 files changed, 17 insertions(+), 6 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 649c29e..edea1ff 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -60,6 +60,11 @@ SGI Irix-6.x mips-*-irix6*
VAX running (4.2 - 4.3 Reno) BSD vax-*-bsd*
VAX running Ultrix vax-*-ultrix*
+* Catch syscall catches groups of related syscalls.
+
+ Catch syscall command supports catching a group of related
+ syscalls using the 'group:' or 'g:' prefix.
+
*** Changes in GDB 7.8
* New command line options
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 8520361..9bd3519 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -16736,11 +16736,11 @@ If REGEX is given, only stop for libraries matching the regular expression."),
CATCH_PERMANENT,
CATCH_TEMPORARY);
add_catch_command ("syscall", _("\
-Catch system calls by their names and/or numbers.\n\
-Arguments say which system calls to catch. If no arguments\n\
-are given, every system call will be caught.\n\
-Arguments, if given, should be one or more system call names\n\
-(if your system supports that), or system call numbers."),
+Catch system calls by their names, groups and/or numbers. Arguments\n\
+say which system calls to catch. If no arguments are given, every\n\
+system call will be caught. Arguments, if given, should be one or\n\
+more system call names (if your system supports that), system call\n\
+groups or system call numbers."),
catch_syscall_command_1,
catch_syscall_completer,
CATCH_PERMANENT,
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 15c2908..ca16e11 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4254,7 +4254,7 @@ A call to @code{exec}. This is currently only available for HP-UX
and @sc{gnu}/Linux.
@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{}
@kindex catch syscall
@cindex break on a system call.
A call to or return from a system call, a.k.a.@: @dfn{syscall}. A
@@ -4289,6 +4289,12 @@ may be useful if @value{GDBN}'s database does not have the complete
list of syscalls on your system (e.g., because @value{GDBN} lags
behind the OS upgrades).
+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
+related syscalls, by passing the argument @code{group:network} to
+@code{catch syscall}.
+
The example below illustrates how this command works if you don't provide
arguments to it:
--
1.9.3
next prev parent reply other threads:[~2014-11-02 19:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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-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 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-02 19:37 ` Gabriel Krisman Bertazi [this message]
2014-11-02 19:45 ` [PATCH 4/4] Update documentation on catching a group of related syscalls Eli Zaretskii
2014-11-12 2:04 ` Gabriel Krisman Bertazi
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-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 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2015-01-15 8:28 ` 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-29 0:19 ` [ping PATCH v2 1/4] Implemement support for groups of syscalls in the xml-syscall interface 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
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=1414956944-8856-5-git-send-email-gabriel@krisman.be \
--to=gabriel@krisman.be \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).