This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/394] New: wierd I/O-error handling in libio
- From: "peak at argo dot troja dot mff dot cuni dot cz" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 20 Sep 2004 22:10:43 -0000
- Subject: [Bug libc/394] New: wierd I/O-error handling in libio
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
1. {new,old}_do_write() & _IO_{new,old}_file_xsputn() cannot handle -1 from
_IO_SYSWRITE() even if -1 appears to be the expected way to signal errors (and
certain functions like fmemopen_write() do that)
2. read errors are recorded (_IO_ERR_SEEN) in _IO_{new,old}_file_overflow() and
_IO_file_xsgetn() (but not in _IO_default_xsgetn()!) while write errors are
recorded on a lower level--in _IO_{new,old}_file_write() (and this is impossible
to do with fopencookie()); are these inconsistencies intentional?
--
Summary: wierd I/O-error handling in libio
Product: glibc
Version: 2.3.3
Status: NEW
Severity: minor
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: peak at argo dot troja dot mff dot cuni dot cz
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=394
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.