public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trt at sas 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: Tue, 01 Sep 2020 12:03:56 +0000	[thread overview]
Message-ID: <bug-26557-131-ltbZgugvvQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26557-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom Truscott <trt at sas dot com> ---
Correction: open_memstream() gives incorrect behavior in all those glibc (2.12,
2.17, 2.28, and also 2.31). The incorrect behavior varies.

Also, fmemopen() gave incorrect behavior in older glibc, but it seems okay now
and our only concern is with open_memstream().

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

  reply	other threads:[~2020-09-01 12:03 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 ` trt at sas dot com [this message]
2021-03-05 15:24 ` [Bug stdio/26557] " pipcet at gmail dot com
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-ltbZgugvvQ@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).