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
--9amGYk9869ThD9tj
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9tNZ9ynjLPm522B0RAhEwAJ4p2HjZw73IvMO609pUE0HfgdxytACfXUeQ
vYBH0ZyqI2EUl2HQmIld6js=
=y72D
-----END PGP SIGNATURE-----
--9amGYk9869ThD9tj--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/