Re: MacOS strerror_r

2011-06-08 Thread Eric Blake
On 06/08/2011 05:38 AM, Eric Blake wrote: > I fixed that, and found the next bug: > > $ ./foo 1 23 > Operation not permitte(34) > $ ./foo 1 24 > Operation not permitted(0) > > Ouch. MacOS is _silently_ writing a NUL byte beyond the array bounds, > if the input buffer size is exactly equal to str

MacOS strerror_r [was: [PATCH 2/2] strerror: work around FreeBSD bug]

2011-06-08 Thread Eric Blake
On 06/07/2011 09:50 PM, Eric Blake wrote: >> strerror(0) misbehavior. Hmm, while FreeBSD was setting EINVAL to make >> the failure explicit, MacOS is claiming success while still outputting >> "Unknown error: 0". I'll fix that with a strstr() test in the .m4 files. > > Oh hideous. > > strerror(