On 08/07/2015 22:22, Garrett Cooper wrote:
> On Jul 8, 2015, at 12:17, Doug Rabson <d...@rabson.org> wrote:
>> As far as I can tell, POSIX doesn't require either EFAULT or any other 
>> behaviour - the text in http://www.open-std.org/jtc1/sc22/open/n4217.pdf 
>> just says, "No errors are defined". Our man page is wrong and any real 
>> program which relies on gettimeofday not faulting when given bad inputs is 
>> broken.
> I would suggest the following: 1. Document behavior in NOTES about
> gettimeofday returning EFAULT with the specific scenarios kib mentioned,
> segfaulting otherwise (wordsmithing the actual info of course). Otherwise, it
> might confuse people who look at the manpage later. 2. I’ll add a `#ifdef
> __FreeBSD__` to the testcase which will then skip it, because it’s easier to
> do that then test undefined behavior that only makes sense on NetBSD.

I am not suggesting this but if our man pages used all capitals to signify
important auxiliary verbs then the ERRORS sections would read as
        The following error codes MAY be set in errno:
Perhaps in that case it would be more clear how 'MAY' differs from 'SHOULD' and
Of course, the manual pages seem to be too sloppy in this respect.

Reference: https://www.ietf.org/rfc/rfc2119.txt

Andriy Gapon
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to