public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pipcet at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/26557] Incorrect behavior with open_memstream in recent version(s) of glibc
Date: Fri, 05 Mar 2021 15:24:53 +0000	[thread overview]
Message-ID: <bug-26557-131-OAtgR42jju@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26557-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26557

pipcet at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pipcet at gmail dot com

--- Comment #2 from pipcet at gmail dot com ---
I'm seeing this as well, I believe:

When the FILE *returned by open_memstream is closed, the buffer that is
returned is truncated to be as large as the current file offset, not the length
of the data that has been written (and also not the actual size of the buffer
that has been allocated).

Furthermore, fseek (file, 0, SEEK_END) does not seek to the end of the written
buffer.

It's possible this behavior is documented in the standard, but it's not
documented in the manpage.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-03-05 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 20:31 [Bug stdio/26557] New: " trt at sas dot com
2020-09-01 12:03 ` [Bug stdio/26557] " trt at sas dot com
2021-03-05 15:24 ` pipcet at gmail dot com [this message]
2022-06-06 16:16 ` 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-26557-131-OAtgR42jju@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).