This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug stdio/17647] New: ftell after ftruncate reports incorrect offset
- From: "siddhesh at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 25 Nov 2014 15:43:05 +0000
- Subject: [Bug stdio/17647] New: ftell after ftruncate reports incorrect offset
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17647
Bug ID: 17647
Summary: ftell after ftruncate reports incorrect offset
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: stdio
Assignee: siddhesh at redhat dot com
Reporter: siddhesh at redhat dot com
Currently we seek to end of file if there are unflushed writes or the
stream is in write mode, to get the current offset for writing in
append mode, which is the end of file. The latter case (i.e. stream
is in write mode, but no unflushed writes) is unnecessary since it
will only happen when the stream has just been flushed, in which case
the recorded offset ought to be reliable.
Removing that case lets ftell give the correct offset when it follows
an ftruncate. The latter truncates the file, but does not change the
file position, due to which it is permissible to call ftell without an
intervening fseek call.
--
You are receiving this mail because:
You are on the CC list for the bug.