public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29546] New: sigdescr_np for SIGEMT is useless
Date: Sat, 03 Sep 2022 11:40:23 +0000 [thread overview]
Message-ID: <bug-29546-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29546
Bug ID: 29546
Summary: sigdescr_np for SIGEMT is useless
Product: glibc
Version: 2.34
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: string
Assignee: unassigned at sourceware dot org
Reporter: bruno at clisp dot org
Target Milestone: ---
Created attachment 14315
--> https://sourceware.org/bugzilla/attachment.cgi?id=14315&action=edit
test case
The function sigdescr_np is supposed to "return the message describing the
signal signum", see
https://www.gnu.org/software/libc/manual/html_node/Signal-Messages.html.
However, for the value SIGEMT, it returns a string without real information.
If a user did not know what SIGEMT means before, he won't know it afterwards.
How to reproduce:
$ gcc -Wall foo.c
$ ./a.out
SIGEMT -> EMT trap
Suggestion: Use the description string "Instruction emulation needed" instead.
That's what is understandable from the FreeBSD man page
https://www.freebsd.org/cgi/man.cgi?sektion=3&query=signal .
Seen on
- Debian GNU/Hurd, with glibc 2.34.
- Linux/sparc64, with glibc 2.33.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-09-03 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 11:40 bruno at clisp dot org [this message]
2022-09-03 11:41 ` [Bug string/29546] " bruno at clisp dot org
2022-09-05 11:34 ` fweimer at redhat dot com
2022-09-06 1:04 ` bruno at clisp dot org
2022-09-06 10:31 ` fweimer at redhat dot com
2022-09-06 11:01 ` bruno at clisp dot org
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=bug-29546-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).