Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Clarify documentation of signal numbers
Date: Thu, 2 Jan 2025 23:27:11 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2501020213450.20821@angie.orcam.me.uk> (raw)
In-Reply-To: <867c7ta6j8.fsf@gnu.org>

On Sat, 21 Dec 2024, Eli Zaretskii wrote:

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

 FWIW I think it would make sense to show signal number information along 
with output from `info signal'.  I wasn't aware even you could use numbers 
rather than names here.

  Maciej

  reply	other threads:[~2025-01-02 23:27 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
2025-01-02 23:27   ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.21.2501020213450.20821@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=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