d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Go to a bit more trouble to make it absolutely clear that malloc(3)

Browse Source 
does not zero the allocated memory.
This commit is contained in:
Peter Wemm 1999-11-12 16:41:21 +00:00
parent bd8ae5d0d7
commit 0d052386ba
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
lib/libc/stdlib/malloc.3
View File

@ -73,6 +73,12 @@ If
.Fn malloc
fails, a NULL pointer is returned.
.Pp
Note that
.Fn malloc
does
.Em NOT
normally initialize the returned memory to zero bytes.
.Pp
The
.Fn calloc
function allocates space for
@ -85,7 +91,8 @@ The result is identical to calling
.Fn malloc
with an argument of
.Dq "number * size" ,
with the exception that the allocated memory is initialized to nul bytes.
with the exception that the allocated memory is explicitly initialized
to zero bytes.
.Pp
The
.Fn realloc
@ -310,7 +317,7 @@ options and symbols for debugger support.
If the program starts to give unusual results, coredump or generally behave
differently without emitting any of the messages listed in the next
section, it is likely because it depends on the storage being filled with
nul bytes. Try running it with
zero bytes. Try running it with
.Dq Z
option set;
if that improves the situation, this diagnosis has been confirmed.