svn commit: r236582 - head/lib/libc/stdlib

[Dag-Erling Smørgrav]

Pawel Jakub Dawidek <pjd at FreeBSD.org> writes:
> Very interesting. However free(3) is always successful. Maybe we need
> more context here, but the sentence above might talk about functions
> that can either succeed or fail and such functions do set errno on
> failure, but we don't know what they do to errno on success - they
> sometimes interact with the errno, free(3) never does.

Even if free() itself never fails, it might have side effects such as
unmapping a slab, logging a KTR event etc. which can modify errno.

DES
-- 
Dag-Erling Smørgrav - des at des.no