On Mon, Oct 21, 2002 at 07:16:55PM -0700, Ulrich Drepper wrote:
> The fault is entirely yours. You're not allowed to look at errno unless
> a function, which is defined to modify error on failure, is reporting it
> failed. Both pipe() calls work just fine and errno has some random
> value which happens to be ESPIPE for you. Read the standard.
right. the perror() giving nonsensical results wasn't the cause of my
problem of course, i was just trying to use it to find out why the pipe
didn't seem to work. turns out that i missed the forest for the trees;
the pipe was being opened for writing from the wrong end...
(as a side note, the code in question was written on a solaris box, and
it seems to Just Work in the wrong direction there, go fig.)
thanks
--sean
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:57 EST