public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug stdio/16724] New: offset computation in ftell is incorrect when a read is followed by a write for files opened in a+ mode
@ 2014-03-18 20:18 siddhesh at redhat dot com
  2014-03-20 14:23 ` [Bug stdio/16724] " erik.m.bray at gmail dot com
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: siddhesh at redhat dot com @ 2014-03-18 20:18 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=16724

            Bug ID: 16724
           Summary: offset computation in ftell is incorrect when a read
                    is followed by a write for files opened in a+ mode
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: stdio
          Assignee: siddhesh at redhat dot com
          Reporter: siddhesh at redhat dot com

ftell reports an incorrect offset when a file opened in a+ mode is first read
from and then written to.  This is because the assumption of _IO_read_end
coinciding with the external file position is not correct when O_APPEND is in
effect.

Fix coming up.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2014-06-13  9:18 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-18 20:18 [Bug stdio/16724] New: offset computation in ftell is incorrect when a read is followed by a write for files opened in a+ mode siddhesh at redhat dot com
2014-03-20 14:23 ` [Bug stdio/16724] " erik.m.bray at gmail dot com
2014-03-20 14:43 ` siddhesh at redhat dot com
2014-03-24 15:49 ` erik.m.bray at gmail dot com
2014-05-27  8:25 ` cvs-commit at gcc dot gnu.org
2014-05-27  8:28 ` siddhesh at redhat dot com
2014-06-13  9:18 ` fweimer at redhat dot com

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).