public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guenther at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15298] open_memstream(): seek-past-end should not change size until write
Date: Sat, 23 Mar 2013 05:34:00 -0000	[thread overview]
Message-ID: <bug-15298-131-Akr3rb3MpT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15298-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15298

--- Comment #1 from Philip Guenther <guenther at gmail dot com> 2013-03-23 05:33:52 UTC ---
The behavior of fseek(fp, offset, SEEK_END) also seems...odd.  My expectation,
given the wording of the spec, is that it would be relative to the buffer
length (as defined by the spec) but it seems to be relative to something bigger
than that, the actual allocated buffer size, perhaps?  Isn't the stream created
by open_memstream() supposed to behave like an in-memory version of a temp
file, so seeks from SEEK_END should be relative to just past the last written
position?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-03-23  5:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-23  4:40 [Bug libc/15298] New: " guenther at gmail dot com
2013-03-23  4:58 ` [Bug libc/15298] " guenther at gmail dot com
2013-03-23  5:34 ` guenther at gmail dot com [this message]
2014-06-13 18:41 ` fweimer at redhat dot com
2015-08-22 20:34 ` [Bug stdio/15298] " jsm28 at gcc dot gnu.org
2020-06-24 15:57 ` tonyb at cybernetics 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-15298-131-Akr3rb3MpT@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).