public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] gdb/doc: extend the documentation for the 'handle' command
@ 2023-02-06 14:57 Andrew Burgess
  0 siblings, 0 replies; only message in thread
From: Andrew Burgess @ 2023-02-06 14:57 UTC (permalink / raw)
  To: gdb-cvs

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=85df9457b72e4a198b4edfc908017612fca59509

commit 85df9457b72e4a198b4edfc908017612fca59509
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Thu Feb 2 11:45:41 2023 +0000

    gdb/doc: extend the documentation for the 'handle' command
    
    The documentation for the 'handle' command does not cover all of the
    features of the command, and in one case, is just wrong.
    
    The user can specify 'all' as signal name, the documentation implies
    that this will change the behaviour of all signals, in reality, this
    changes all signals except SIGINT and SIGTRAP (the signals used by
    GDB).  I've updated the docs to list this limitation.
    
    The 'handle' command also allows the user to specify multiple signals
    for a single command, e.g. 'handle SIGFPE SIGILL nostop pass print',
    however the documentation doesn't describe this, so I've updated the
    docs to describe this feature.

Diff:
---
 gdb/doc/gdb.texinfo | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index c90874a1214..eebb6dd422a 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -6760,13 +6760,14 @@ Set a catchpoint for the indicated signals.  @xref{Set Catchpoints},
 for details about this command.
 
 @kindex handle
-@item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]}
-Change the way @value{GDBN} handles signal @var{signal}.  The @var{signal}
-can be the number of a signal or its name (with or without the
-@samp{SIG} at the beginning); a list of signal numbers of the form
-@samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the
-known signals.  Optional arguments @var{keywords}, described below,
-say what change to make.
+@item handle @var{signal} @r{[} @var{signal} @dots{} @r{]} @r{[}@var{keywords}@dots{}@r{]}
+Change the way @value{GDBN} handles each @var{signal}.  Each
+@var{signal} can be the number of a signal or its name (with or
+without the @samp{SIG} at the beginning); a list of signal numbers of
+the form @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning
+all the known signals, except @code{SIGINT} and @code{SIGTRAP}, which
+are used by @value{GDBN}.  Optional argument @var{keywords}, described
+below, say what changes to make to all of the specified signals.
 @end table
 
 @c @group

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-02-06 14:57 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-06 14:57 [binutils-gdb] gdb/doc: extend the documentation for the 'handle' command Andrew Burgess

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).