fix unlikely corner cases in getopt's message printing
authorRich Felker <dalias@aerifal.cx>
Tue, 16 Feb 2016 18:27:24 +0000 (13:27 -0500)
committerRich Felker <dalias@aerifal.cx>
Tue, 16 Feb 2016 18:27:24 +0000 (13:27 -0500)
commitef2b5e9f13a7f216d6d64aeccc6b33c1262faece
treec2a4cc48802e53ce387db8c6cd279c1250cadd98
parent10a17dfbad2c267d885817abc9c7589fc7ff630b
fix unlikely corner cases in getopt's message printing

like fputs (see commit 10a17dfbad2c267d885817abc9c7589fc7ff630b), the
message printing code for getopt assumed that fwrite only returns 0 on
failure, but it can also happen on success if the total length to be
written is zero. programs with zero-length argv[0] were affected.

commit 500c6886c654fd45e4926990fee2c61d816be197 introduced this
problem in getopt by fixing the fwrite behavior to conform to the
requirements of ISO C. previously the wrong expectations of the getopt
code were met by the fwrite implementation.
src/misc/getopt.c