public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29530] segfault in printf handling thousands separator Date: Tue, 30 Aug 2022 08:48:43 +0000 [thread overview] Message-ID: <bug-29530-131-pohY7DWos3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29530-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29530 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.31/master branch has been updated by Florian Weimer <fw@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c8f2a3e8038232f7707d11b4629f5d5cf32244fc commit c8f2a3e8038232f7707d11b4629f5d5cf32244fc Author: Andreas Schwab <schwab@suse.de> Date: Mon Aug 29 15:05:40 2022 +0200 Add test for bug 29530 This tests for a bug that was introduced in commit edc1686af0 ("vfprintf: Reuse work_buffer in group_number") and fixed as a side effect of commit 6caddd34bd ("Remove most vfprintf width/precision-dependent allocations (bug 14231, bug 26211)."). (cherry picked from commit ca6466e8be32369a658035d69542d47603e58a99) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-30 8:48 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 [this message] 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
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-pohY7DWos3@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: linkBe 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).