This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 02/19/2018 08:12 PM, Zack Weinberg wrote:
On Mon, Feb 19, 2018 at 1:32 PM, Florian Weimer <fweimer@redhat.com> wrote:On 02/11/2018 07:07 PM, Andreas Schwab wrote:AFAICS, this is an area where we are not conforming to the C standard (the EOF indicator is supposed to be sticking, see fgetc, and only clearerr can fix that).But is this actually observable without violating any of the stream synchronization requirements, or relying on implementation-defined behavior of file descriptors?I think so, see the test case in https://sourceware.org/ml/libc-alpha/2018-02/msg00420.html .
Do you mean the on in this patch: https://sourceware.org/ml/libc-alpha/2018-02/msg00416.htmlI believe the test case is invalid because interleaving file access in this way requires that fseek is used before reading any data, and this will clear the EOF indicator.
Thanks, Florian
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |