public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "samuel.thibault@ens-lyon.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug hurd/29545] New: strerrorname_np returns NULL for some defined errno values
Date: Sat, 03 Sep 2022 09:00:19 +0000 [thread overview]
Message-ID: <bug-29545-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29545
Bug ID: 29545
Summary: strerrorname_np returns NULL for some defined errno
values
Product: glibc
Version: 2.34
Status: NEW
Severity: normal
Priority: P2
Component: hurd
Assignee: unassigned at sourceware dot org
Reporter: samuel.thibault@ens-lyon.org
CC: samuel.thibault@ens-lyon.org, tschwinge at sourceware dot org
Target Milestone: ---
Created attachment 14314
--> https://sourceware.org/bugzilla/attachment.cgi?id=14314&action=edit
testcase
From Bruno Haible <bruno@clisp.org>:
The function strerrorname_np is supposed to return non-NULL for all defined
errno values.
https://www.gnu.org/software/libc/manual/html_node/Error-Messages.html
On Hurd, for the errnos with names
ED_*
EKERN_*
EMACH_*
EMIG_*
it returns NULL.
How to reproduce:
$ gcc -Wall foo.c
$ ./a.out
Seen on Debian GNU/Hurd, with glibc 2.34.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-09-03 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 9:00 samuel.thibault@ens-lyon.org [this message]
2022-09-03 9:02 ` [Bug hurd/29545] " samuel.thibault@ens-lyon.org
2022-09-03 11:37 ` bruno at clisp dot org
2022-09-08 1:47 ` bruno at clisp dot org
2022-09-08 7:39 ` schwab@linux-m68k.org
2023-06-25 16:11 ` bruno at clisp dot org
2023-07-03 19:37 ` adhemerval.zanella at linaro dot org
2023-07-03 20:21 ` 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-29545-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).