public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/30112] [bisected] glibc 2.37 fails to print IPv6 adresses since 642933158e7cf072d873231b1a9bb03291f2b989
Date: Mon, 13 Feb 2023 03:18:40 +0000 [thread overview]
Message-ID: <bug-30112-131-jUn00ihjie@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30112-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30112
--- Comment #3 from Sam James <sam at gentoo dot org> ---
(In reply to Sam James from comment #2)
> I think this might be UB in iproute2 instead.
> [...]
Reported at
https://lore.kernel.org/netdev/0011AC38-4823-4D0A-8580-B108D08959C2@gentoo.org/T/#u.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-13 3:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 21:15 [Bug string/30112] New: [bisected] glibc 2.37 fails to print IPv6 adresses freswa at archlinux dot org
2023-02-10 21:15 ` [Bug string/30112] " freswa at archlinux dot org
2023-02-11 19:25 ` vmlinuz386 at gmail dot com
2023-02-12 2:56 ` sam at gentoo dot org
2023-02-12 3:24 ` [Bug string/30112] [bisected] glibc 2.37 fails to print IPv6 adresses since 642933158e7cf072d873231b1a9bb03291f2b989 sam at gentoo dot org
2023-02-12 17:47 ` dilfridge at gentoo dot org
2023-02-12 21:21 ` flo at geekplace dot eu
2023-02-13 2:56 ` sam at gentoo dot org
2023-02-13 3:18 ` sam at gentoo dot org [this message]
2023-02-13 9:20 ` freswa at archlinux 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-30112-131-jUn00ihjie@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).