public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29530] segfault in printf handling thousands separator
Date: Sat, 06 May 2023 23:11:50 +0000 [thread overview]
Message-ID: <bug-29530-131-dcaXJ95s2H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29530-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29530
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ppluzhnikov at google dot com
Resolution|--- |FIXED
Target Milestone|--- |2.32
--- Comment #9 from Paul Pluzhnikov <ppluzhnikov at google dot com> ---
Fixed by https://sourceware.org/git/?p=glibc.git;a=commit;h=6caddd34bd
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-05-06 23:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 0:27 [Bug libc/29530] New: " godlygeek at gmail dot com
2022-08-29 12:24 ` [Bug libc/29530] " schwab@linux-m68k.org
2022-08-29 12:24 ` schwab@linux-m68k.org
2022-08-29 12:33 ` adhemerval.zanella at linaro dot org
2022-08-29 12:58 ` schwab@linux-m68k.org
2022-08-29 15:06 ` cvs-commit at gcc dot gnu.org
2022-08-30 8:45 ` cvs-commit at gcc dot gnu.org
2022-08-30 8:48 ` cvs-commit at gcc dot gnu.org
2022-08-30 9:20 ` cvs-commit at gcc dot gnu.org
2022-08-30 11:08 ` cvs-commit at gcc dot gnu.org
2023-05-06 23:11 ` ppluzhnikov at google dot com [this message]
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-29530-131-dcaXJ95s2H@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).