Dag-Erling Smorgrav <[EMAIL PROTECTED]> wrote:
>
>Don't use err() indiscriminately after a malloc() failure; malloc()
>doesn't set errno.

When I looked at malloc(3) I decided that it relied on sbrk(2) to set
errno if it returned 0. Is this wrong? i.e. can it return 0 without
a failed syscall?

Tony.
-- 
f.a.n.finch   [EMAIL PROTECTED]   [EMAIL PROTECTED]
Winner, International Obfuscated C Code Competition 1998


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to