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] New: Incorrect behavior with open_memstream in recent version(s) of glibc Date: Mon, 31 Aug 2020 20:31:52 +0000 [thread overview] Message-ID: <bug-26557-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26557 Bug ID: 26557 Summary: Incorrect behavior with open_memstream in recent version(s) of glibc Product: glibc Version: 2.28 Status: UNCONFIRMED Severity: normal Priority: P2 Component: stdio Assignee: unassigned at sourceware dot org Reporter: trt at sas dot com Target Milestone: --- Created attachment 12812 --> https://sourceware.org/bugzilla/attachment.cgi?id=12812&action=edit memstream-test.c The attached memstream-test.c gives expected fseek() behavior on streams created with fopen() and with fmemopen(), and also with open_memstream in glibc 2.12 and 2.17. But in glibc 2.28 an open_memstream() gives incorrect behavior -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-08-31 20:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-31 20:31 trt at sas dot com [this message] 2020-09-01 12:03 ` [Bug stdio/26557] " trt at sas dot com 2021-03-05 15:24 ` 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@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: linkBe 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).