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 stdio/26211] printf integer overflow calculating allocation size
Date: Mon, 29 Aug 2022 15:06:46 +0000 [thread overview]
Message-ID: <bug-26211-131-G36JHVFxr4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26211-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26211
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andreas Schwab <schwab@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ca6466e8be32369a658035d69542d47603e58a99
commit ca6466e8be32369a658035d69542d47603e58a99
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).").
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-29 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 23:03 [Bug stdio/26211] New: " jsm28 at gcc dot gnu.org
2020-07-07 14:54 ` [Bug stdio/26211] " cvs-commit at gcc dot gnu.org
2020-07-07 14:57 ` jsm28 at gcc dot gnu.org
2022-08-29 15:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-30 8:23 ` cvs-commit at gcc dot gnu.org
2022-08-30 8:45 ` 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 9:20 ` cvs-commit at gcc dot gnu.org
2022-08-30 11:07 ` cvs-commit at gcc dot gnu.org
2022-08-30 11:08 ` cvs-commit at gcc dot gnu.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-26211-131-G36JHVFxr4@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).