public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: extend the documentation for the 'handle' command
Date: Thu, 02 Feb 2023 16:19:17 +0200	[thread overview]
Message-ID: <837cx0xi8q.fsf@gnu.org> (raw)
In-Reply-To: <d485111cf21d559d3db32bde4eadb34412a20c50.1675338730.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Thu, 2 Feb 2023 11:52:25 +0000)

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

  reply	other threads:[~2023-02-02 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 11:52 Andrew Burgess
2023-02-02 14:19 ` Eli Zaretskii [this message]
2023-02-06 14:57   ` Andrew Burgess

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=837cx0xi8q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --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).