public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bnnf at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/12701] scanf accepts non-matching input
Date: Fri, 05 Mar 2021 15:27:45 +0000 [thread overview]
Message-ID: <bug-12701-131-eUTCZJ3mV1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12701-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12701
mark <bnnf at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bnnf at yahoo dot com
--- Comment #22 from mark <bnnf at yahoo dot com> ---
Yes I understand pushbacks.
Scanning "0xz" for %x results in an input item of "0x" with "z" pushed back
into the unread buffer. The bug has nothing to do with pushbacks, because the
right data is pushed back. The bug is that a non-matching input item is treated
as a match rather than a matching error.
Perhaps you thought I was saying the input item should be "0", successfully
converted, with "x" as the next unread character in the buffer. Of course this
is wrong and I do not believe such a thing.
https://www.targetedwebtraffic.com/product-category/website-traffic/
Apparently you only read the first quoted paragraph and not the second:
> > - the input item "0x" is not a matching sequence, so the execution of
> > the whole directive fails;
>
> Correct
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-05 15:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 15:13 [Bug libc/12701] New: " bugdal at aerifal dot cx
2011-05-02 1:40 ` [Bug libc/12701] " drepper.fsp at gmail dot com
2011-05-02 2:36 ` bugdal at aerifal dot cx
2011-05-03 0:31 ` drepper.fsp at gmail dot com
2011-05-03 0:40 ` bugdal at aerifal dot cx
2011-05-03 1:14 ` drepper.fsp at gmail dot com
2011-05-03 2:24 ` bugdal at aerifal dot cx
2011-09-25 4:42 ` bugdal at aerifal dot cx
2011-10-29 17:14 ` drepper.fsp at gmail dot com
2011-10-29 21:24 ` bugdal at aerifal dot cx
2011-10-29 21:37 ` drepper.fsp at gmail dot com
2011-10-29 22:04 ` ldv at altlinux dot org
2011-10-30 5:43 ` bugdal at aerifal dot cx
2012-02-21 2:12 ` [Bug stdio/12701] " jsm28 at gcc dot gnu.org
2012-03-17 20:39 ` bugdal at aerifal dot cx
2012-03-18 17:17 ` jsm28 at gcc dot gnu.org
2012-04-18 5:23 ` bugdal at aerifal dot cx
2012-11-26 8:26 ` allachan at au1 dot ibm.com
2014-06-13 14:54 ` fweimer at redhat dot com
2014-06-27 14:00 ` fweimer at redhat dot com
2021-02-10 19:30 ` bnnf-yellowbot at blurcompany dot com
2021-03-05 15:27 ` bnnf at yahoo dot com [this message]
2021-09-15 2:40 ` namboru at jasaseo dot one
2023-07-18 11:44 ` vincent-srcware at vinc17 dot net
2023-07-18 12:01 ` vincent-srcware at vinc17 dot net
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-12701-131-eUTCZJ3mV1@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).