public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/14771] add length sanity check to snprintf Date: Fri, 18 Oct 2013 13:52:00 -0000 [thread overview] Message-ID: <bug-14771-131-ttEOBuXb9J@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14771-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14771 --- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- The Austin Group appears to have failed to address the conflict with C11 semantics. Is the Austin Group / WG14 liaison taking this up with WG14, if the Austin Group view is that the C11 specifications are defective? A fortification check obviously doesn't address the POSIX semantics, so a separate bug would need opening for those if this one is considered to be about fortification only. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-18 13:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-26 10:06 [Bug stdio/14771] New: " fweimer at redhat dot com 2013-10-08 15:55 ` [Bug stdio/14771] " neleai at seznam dot cz 2013-10-08 23:07 ` bugdal at aerifal dot cx 2013-10-08 23:18 ` bugdal at aerifal dot cx 2013-10-18 11:24 ` fweimer at redhat dot com 2013-10-18 12:31 ` fweimer at redhat dot com 2013-10-18 13:52 ` joseph at codesourcery dot com [this message] 2014-06-13 10:46 ` fweimer at redhat dot com 2022-07-19 17:27 ` jsm28 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-14771-131-ttEOBuXb9J@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).