public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nfxjfg at googlemail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/17829] New: Incorrect handling of precision specifier in printf family Date: Mon, 12 Jan 2015 04:32:00 -0000 [thread overview] Message-ID: <bug-17829-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17829 Bug ID: 17829 Summary: Incorrect handling of precision specifier in printf family Product: glibc Version: 2.19 Status: NEW Severity: critical Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: nfxjfg at googlemail dot com CC: drepper.fsp at gmail dot com The following program shows no output: #include <stdio.h> #include <limits.h> int main(int argc, char **argv) { printf("%.*s\n", INT_MAX, "hi"); return 0; } The precision given is INT_MAX; this should turn the precision specifier into a no-OP, equivalent to 'printf("%s\n", "hi");'. Making the precision value somewhat lower seems to make it work. snprintf() seems to have a similar issue, but the failure seems to start with even lower precision values. Other libcs handle this correctly (I tested mingw-w64 and musl). Using glibc 2.19-13 on Debian 32 bit x86. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-01-12 4:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-12 4:32 nfxjfg at googlemail dot com [this message] 2015-01-12 4:33 ` [Bug libc/17829] " nfxjfg at googlemail dot com 2015-01-12 17:52 ` [Bug stdio/17829] " jsm28 at gcc dot gnu.org 2015-01-29 13:00 ` fweimer at redhat dot com 2015-02-18 14:27 ` fweimer at redhat dot com 2015-02-18 14:33 ` carlos at redhat dot com 2015-02-18 17:26 ` nfxjfg at googlemail dot com 2020-07-07 14:54 ` cvs-commit at gcc dot gnu.org 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 9:20 ` cvs-commit at gcc dot gnu.org 2022-08-30 11:07 ` 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-17829-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: 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).