public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/30068] incorrect printf output for integers with thousands separator and width field Date: Thu, 02 Feb 2023 08:54:28 +0000 [thread overview] Message-ID: <bug-30068-131-6OznwlhTcT@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30068-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30068 --- Comment #4 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> --- I suspect that the padding amount is computed ignoring the thousands separators, so that the increasing of the width would be equal to the total length of the thousands separator. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-02 8:54 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-02 1:16 [Bug stdio/30068] New: " vincent-srcware at vinc17 dot net 2023-02-02 1:17 ` [Bug stdio/30068] " vincent-srcware at vinc17 dot net 2023-02-02 2:25 ` vincent-srcware at vinc17 dot net 2023-02-02 7:51 ` freswa at archlinux dot org 2023-02-02 8:54 ` vincent-srcware at vinc17 dot net [this message] 2023-02-02 11:25 ` xry111 at xry111 dot site 2023-02-02 12:40 ` xry111 at xry111 dot site 2023-02-02 14:27 ` carlos at redhat dot com 2023-02-02 14:27 ` carlos at redhat dot com 2023-02-02 16:41 ` sam at gentoo dot org 2023-02-02 22:17 ` siddhesh at sourceware dot org 2023-02-02 22:19 ` siddhesh at sourceware dot org 2023-02-03 11:56 ` [Bug stdio/30068] incorrect printf output for integers with thousands separator and width field (CVE-2023-25139) siddhesh at sourceware dot org 2023-02-06 15:24 ` carlos at redhat dot com 2023-02-06 18:03 ` carlos at redhat dot com 2023-02-08 1:32 ` carlos at redhat 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-30068-131-6OznwlhTcT@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).