public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
* [PATCH] gdb/doc: extend the documentation for the 'handle' command
@ 2023-02-02 11:52 Andrew Burgess
  2023-02-02 14:19 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Burgess @ 2023-02-02 11:52 UTC (permalink / raw)
  To: gdb-patches; +Cc: Andrew Burgess

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.
---
 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 03033c7f9e3..30b699f3d31 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -6760,13 +6760,14 @@
 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

base-commit: cded17bfca35566fa4d36e9ec06fa071bd7dab17
-- 
2.25.4


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] gdb/doc: extend the documentation for the 'handle' command
  2023-02-02 11:52 [PATCH] gdb/doc: extend the documentation for the 'handle' command Andrew Burgess
@ 2023-02-02 14:19 ` Eli Zaretskii
  2023-02-06 14:57   ` Andrew Burgess
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2023-02-02 14:19 UTC (permalink / raw)
  To: Andrew Burgess; +Cc: gdb-patches

> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Thu,  2 Feb 2023 11:52:25 +0000
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
> 
> 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.
> ---
>  gdb/doc/gdb.texinfo | 15 ++++++++-------
>  1 file changed, 8 insertions(+), 7 deletions(-)

Thanks, this is okay.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] gdb/doc: extend the documentation for the 'handle' command
  2023-02-02 14:19 ` Eli Zaretskii
@ 2023-02-06 14:57   ` Andrew Burgess
  0 siblings, 0 replies; 3+ messages in thread
From: Andrew Burgess @ 2023-02-06 14:57 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: gdb-patches

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Andrew Burgess <aburgess@redhat.com>
>> Date: Thu,  2 Feb 2023 11:52:25 +0000
>> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>> 
>> 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.
>> ---
>>  gdb/doc/gdb.texinfo | 15 ++++++++-------
>>  1 file changed, 8 insertions(+), 7 deletions(-)
>
> Thanks, this is okay.

Thanks, pushed.

Andrew


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-02-06 14:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-02 11:52 [PATCH] gdb/doc: extend the documentation for the 'handle' command Andrew Burgess
2023-02-02 14:19 ` Eli Zaretskii
2023-02-06 14:57   ` 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).