A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=657 ====================================================================== Reported By: philip-guenther Assigned To: ajosey ====================================================================== Project: 1003.1(2008)/Issue 7 Issue ID: 657 Category: System Interfaces Type: Clarification Requested Severity: Objection Priority: normal Status: Interpretation Required Name: Philip Guenther Organization: OpenBSD User Reference: Section: fmemopen Page Number: 867 Line Number: 28775 Interp Status: Pending Final Accepted Text: https://austingroupbugs.net/view.php?id=657#c6535 ====================================================================== Date Submitted: 2013-02-08 22:46 UTC Last Modified: 2023-10-16 22:15 UTC ====================================================================== Summary: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0000396 fmemopen vs. 'b' mode flag related to 0000456 mandate binary mode of fmemopen related to 0000818 fmemopen should allow 0-size buffer ======================================================================
---------------------------------------------------------------------- (0006539) Don Cragun (manager) - 2023-10-16 22:15 https://austingroupbugs.net/view.php?id=657#c6539 ---------------------------------------------------------------------- re:https://austingroupbugs.net/view.php?id=657#c6536 Yes,. Except for the change of making mode "w" truncate the buffer (as well as "w+". Looking at the glib code we found that the original implementation of fmemopen() did truncate in both cases, but that was changed along with a note saying the change was make to conform to POSIX. The original POSIX text was derived from the glib man page for fmemopen() and it was not verified against the source at that time. We have asked the maintainers if they are willing to go back to the original implementation; if they are not we can change this back to the current behavior (or make it unspecified) before the interpretation is finalized. Note that the BSD implementation of fmemopen() does truncate the buffer for both "w" and "w+". Issue History Date Modified Username Field Change ====================================================================== 2013-02-08 22:46 philip-guentherNew Issue 2013-02-08 22:46 philip-guentherStatus New => Under Review 2013-02-08 22:46 philip-guentherAssigned To => ajosey 2013-02-08 22:46 philip-guentherName => Philip Guenther 2013-02-08 22:46 philip-guentherOrganization => OpenBSD 2013-02-08 22:46 philip-guentherSection => fmemopen 2013-02-08 22:46 philip-guentherPage Number => 867 2013-02-08 22:46 philip-guentherLine Number => 28775 2013-02-14 16:55 eblake Relationship added related to 0000396 2013-02-14 16:55 eblake Relationship added related to 0000456 2013-03-28 23:54 philip-guentherNote Added: 0001506 2014-01-30 04:06 eblake Relationship added related to 0000818 2023-10-16 16:06 geoffclare Note Added: 0006535 2023-10-16 16:07 geoffclare Interp Status => Pending 2023-10-16 16:07 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=657#c6535 2023-10-16 16:07 geoffclare Status Under Review => Interpretation Required 2023-10-16 16:07 geoffclare Resolution Open => Accepted As Marked 2023-10-16 16:08 geoffclare Note Edited: 0006535 2023-10-16 16:09 geoffclare Note Edited: 0006535 2023-10-16 16:09 geoffclare Tag Attached: issue8 2023-10-16 18:29 philip-guentherNote Added: 0006536 2023-10-16 22:15 Don Cragun Note Added: 0006539 ======================================================================
