From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31116 invoked by alias); 14 Aug 2008 16:55:12 -0000 Received: (qmail 30730 invoked by uid 48); 14 Aug 2008 16:53:49 -0000 Date: Thu, 14 Aug 2008 16:55:00 -0000 Message-ID: <20080814165349.30729.qmail@sourceware.org> From: "ebb9 at byu dot net" To: glibc-bugs@sources.redhat.com In-Reply-To: <20080522062629.6544.witekfl@poczta.onet.pl> References: <20080522062629.6544.witekfl@poczta.onet.pl> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/6544] fseek(..., 0, SEEK_END) doesn't work as it should on fmemopen's FILE X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00083.txt.bz2 ------- Additional Comments From ebb9 at byu dot net 2008-08-14 16:53 ------- POSIX 200x is standardizing fmemopen with semantics that match neither the original implementation, nor your new binary mode (in particular, the POSIX wording states concerning the mode argument "The character 'b' shall have no effect"). I also raised some questions as to whether glibc's fmemopen is buggy in relation to other stream behavior: https://www.opengroup.org/sophocles/show_mail.tpl?CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=10782 -- http://sourceware.org/bugzilla/show_bug.cgi?id=6544 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.