------- Comment #1 from tkoenig at gcc dot gnu dot org 2006-12-15 21:14 -------
For writing, I think this fails because we
- write a bogus record marker with value 0
- write out the data
- write out the trailing record marker
- seek to the first record marker
- write out its value
- seek past the end
These seeks actually translate to OS calls, which of course fails
for pipes.
For reading, there is another problem: If I
- redirect the output from a to a file
- cat it into the named pipe
- read it using b
it gives a bogus "corrupt unformatted sequential file" error,
for a reason that I don't understand at the moment.
Ouch. This one is nasty.
--
tkoenig at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-12-15 21:14:51
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30162
