mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Possible oversight in setvbuf()
Date: Fri, 13 Jul 2018 16:40:52 +0200	[thread overview]
Message-ID: <20180713144052.GA13099@voyager> (raw)

Hi all,

ungetc() seems to depend on f->buf pointing UNGET bytes into a valid
array. fdopen() will provide such a thing. However, setvbuf() will set
f->buf to the very start of the user provided buffer. Bizarrely, UNGET
is deducted from the buffer size, but not added to the pointer.
Oversight or intentional?

Ciao,
Markus


             reply	other threads:[~2018-07-13 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 14:40 Markus Wichmann [this message]
2018-07-13 21:31 ` Rich Felker
2018-07-13 21:46   ` Christopher Friedt
2018-07-13 22:06     ` Rich Felker
2018-07-13 22:19       ` Christopher Friedt
2018-07-14  2:03         ` Rich Felker
2018-07-14  2:05 ` Rich Felker

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=20180713144052.GA13099@voyager \
    --to=nullplan@gmx.net \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).