sed bug on seekable stdin

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

POSIX requires the following behavior [1]:

$ rm -Rf file
$ echo a b | tr ' ' '\n' > file
$ (sed -n 1q; cat) < file
b

And on systems like Solaris, where exit() implicitly calls fclose(stdin),
this is the case.  But on systems like Linux, where glibc does not do
this, and where Ulrich is unwilling to change glibc to help out[2], sed
fails to restore the fd's current offset to the next unprocessed byte,
meaning that cat sees EOF instead of the correct "b\n".

The solution is simple - before any use of exit(EXIT_SUCCESS) (or before
returning from main), you must ensure that you call fclose(stdin).

[1] http://www.opengroup.org/susv3xcu/xcu_chap01.html, section 1.11, input
files
[2] http://sources.redhat.com/bugzilla/show_bug.cgi?id=3746

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFhLws84KuGfSFAYARAs5RAJwK30oA1+4QTSmycFA0ZB2xsoYaKgCeOtEl
38cXzLXiSRLmmL/TTI87JdM=
=CTu8
-----END PGP SIGNATURE-----