From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Clarify documentation of signal numbers
Date: Sat, 21 Dec 2024 08:34:19 +0200 [thread overview]
Message-ID: <867c7ta6j8.fsf@gnu.org> (raw)
In-Reply-To: <20241220201940.3235367-1-tromey@adacore.com> (message from Tom Tromey on Fri, 20 Dec 2024 13:19:40 -0700)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Fri, 20 Dec 2024 13:19:40 -0700
>
> A user was confused by the meaning of signal numbers in the gdb CLI.
> For instance, when using "signal 3", exactly which signal is
> delivered? Is it always 3, or is it always SIGQUIT?
>
> This patch attempts to clarify the documentation here.
>
> Let me know what you think. I'm not sure this is phrased in the
> clearest way possible.
It's clear enough, IMO. But I wonder whether we should simply have a
table of POSIX signal numbers 1-15 and the corresponding names, as GDB
converts them. Then the examples you show (which describe just some
of those conversions) will be unnecessary, and we only need to say
that signals 1-15 are interpreted as POSIX says and as shown in the
table. A table is IMO better because if someone uses GDB on a
non-POSIX platform, they don't necessarily have easy access to header
files on a POSIX platform to find out which signal is, say, signal 11.
So the only way for them to know is to type
(gdb) handle 11 stop
and see what GDB shows in response, which is not always
possible/convenient.
Thanks.
next prev parent reply other threads:[~2024-12-21 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 20:19 Tom Tromey
2024-12-21 6:34 ` Eli Zaretskii [this message]
2025-01-02 23:27 ` Maciej W. Rozycki
2025-01-06 17:51 ` Tom Tromey
2025-01-06 18:37 ` Eli Zaretskii
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=867c7ta6j8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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