man3/malloc.3

@@ -58,7 +58,6 @@ Feature Test Macro Requirements for glibc (see
         _GNU_SOURCE
 .fi
 .SH DESCRIPTION
-.SS malloc()
 The
 .BR malloc ()
 function allocates
@@ -69,24 +68,27 @@ If
 .I size
 is 0, then
 .BR malloc ()
-returns a unique pointer value that can later be successfully passed to
+returns either NULL,
+.\" glibc does this:
+or a unique pointer value that can later be successfully passed to
 .BR free ().
-(See "Nonportable behavior" for portability issues.)
-.SS free()
+.PP
 The
 .BR free ()
 function frees the memory space pointed to by
 .IR ptr ,
 which must have been returned by a previous call to
-.BR malloc ()
-or related functions.
+.BR malloc (),
+.BR calloc (),
+or
+.BR realloc ().
 Otherwise, or if
-.I ptr
-has already been freed, undefined behavior occurs.
+.I free(ptr)
+has already been called before, undefined behavior occurs.
 If
 .I ptr
 is NULL, no operation is performed.
-.SS calloc()
+.PP
 The
 .BR calloc ()
 function allocates memory for an array of
@@ -101,9 +103,10 @@ or
 .I size
 is 0, then
 .BR calloc ()
-returns a unique pointer value that can later be successfully passed to
+returns either NULL,
+.\" glibc does this:
+or a unique pointer value that can later be successfully passed to
 .BR free ().
-.PP
 If the multiplication of
 .I nmemb
 and
@@ -121,7 +124,7 @@ with the result that an incorrectly sized block of memory would be allocated:
 malloc(nmemb * size);
 .EE
 .in
-.SS realloc()
+.PP
 The
 .BR realloc ()
 function changes the size of the memory block pointed to by
@@ -129,42 +132,39 @@ function changes the size of the memory block pointed to by
 to
 .I size
 bytes.
-The contents of the memory
-will be unchanged in the range from the start of the region
+The contents will be unchanged in the range from the start of the region
 up to the minimum of the old and new sizes.
 If the new size is larger than the old size, the added memory will
 .I not
 be initialized.
-.PP
 If
 .I ptr
 is NULL, then the call is equivalent to
 .IR malloc(size) ,
 for all values of
-.IR size .
-.PP
-If
+.IR size ;
+if
 .I size
 is equal to zero,
 and
 .I ptr
 is not NULL, then the call is equivalent to
 .I free(ptr)
-(but see "Nonportable behavior" for portability issues).
-.PP
+(this behavior is nonportable; see NOTES).
 Unless
 .I ptr
 is NULL, it must have been returned by an earlier call to
-.B malloc
-or related functions.
+.BR malloc (),
+.BR calloc (),
+or
+.BR realloc ().
 If the area pointed to was moved, a
 .I free(ptr)
 is done.
-.SS reallocarray()
+.PP
 The
 .BR reallocarray ()
-function changes the size of (and possibly moves)
-the memory block pointed to by
+function changes the size of the memory block pointed to by
 .I ptr
 to be large enough for an array of
 .I nmemb
@@ -174,9 +174,7 @@ bytes.
 It is equivalent to the call
 .PP
 .in +4n
-.EX
-realloc(ptr, nmemb * size);
-.EE
+    realloc(ptr, nmemb * size);
 .in
 .PP
 However, unlike that
@@ -186,46 +184,60 @@ call,
 fails safely in the case where the multiplication would overflow.
 If such an overflow occurs,
 .BR reallocarray ()
-returns an error.
+returns NULL, sets
+.I errno
+to
+.BR ENOMEM ,
+and leaves the original block of memory unchanged.
 .SH RETURN VALUE
 The
-.BR malloc (),
-.BR calloc (),
-.BR realloc (),
+.BR malloc ()
 and
-.BR reallocarray ()
+.BR calloc ()
 functions return a pointer to the allocated memory,
-which is suitably aligned for any type that fits into
-the requested size or less.
-On error, these functions return NULL and set
-.IR errno .
-Attempting to allocate more than
-.B PTRDIFF_MAX
-bytes is considered an error, as an object that large
-could cause later pointer subtraction to overflow.
+which is suitably aligned for any built-in type.
+On error, these functions return NULL.
+NULL may also be returned by a successful call to
+.BR malloc ()
+with a
+.I size
+of zero,
+or by a successful call to
+.BR calloc ()
+with
+.I nmemb
+or
+.I size
+equal to zero.
 .PP
 The
 .BR free ()
-function returns no value, and preserves
-.IR errno .
+function returns no value.
 .PP
 The
 .BR realloc ()
-and
-.BR reallocarray ()
-functions return NULL if
-.I ptr
-is not NULL and the requested size is zero;
-this is not considered an error.
-(See "Nonportable behavior" for portability issues.)
-Otherwise, the returned pointer may be the same as
+function returns a pointer to the newly allocated memory, which is suitably
+aligned for any built-in type, or NULL if the request failed.
+The returned pointer may be the same as
 .IR ptr
 if the allocation was not moved
 (e.g., there was room to expand the allocation in-place), or different from
 .IR ptr
 if the allocation was moved to a new address.
-If these functions fail,
-the original block is left untouched; it is not freed or moved.
+If
+.I size
+was equal to 0, either NULL or a pointer suitable to be passed to
+.BR free ()
+is returned.
+If
+.BR realloc ()
+fails, the original block is left untouched; it is not freed or moved.
+.PP
+On success, the
+.BR reallocarray ()
+function returns a pointer to the newly allocated memory.
+On failure,
+it returns NULL and the original block of memory is left untouched.
 .SH ERRORS
 .BR calloc (),
 .BR malloc (),
@@ -245,16 +257,6 @@ limit described in
 .SH VERSIONS
 .BR reallocarray ()
 first appeared in glibc in version 2.26.
-.PP
-.BR malloc ()
-and related functions rejected sizes greater than
-.B PTRDIFF_MAX
-starting in glibc 2.30.
-.PP
-.BR free ()
-preserved
-.I errno
-starting in glibc 2.33.
 .SH ATTRIBUTES
 For an explanation of the terms used in this section, see
 .BR attributes (7).
@@ -342,27 +344,30 @@ or
 .BR mmap (2)),
 and managed with its own mutexes.
 .PP
-If your program uses a private memory allocator,
-it should do so by replacing
+SUSv2 requires
 .BR malloc (),
-.BR free (),
 .BR calloc (),
 and
-.BR realloc ().
-The replacement functions must implement the documented glibc behaviors,
-including
+.BR realloc ()
+to set
 .I errno
-handling, size-zero allocations, and overflow checking;
-otherwise, other library routines may crash or operate incorrectly.
-For example, if the replacement
-.IR free ()
-does not preserve errno, then seemingly unrelated library routines may
-fail without having a valid reason in
+to
+.B ENOMEM
+upon failure.
+Glibc assumes that this is done
+(and the glibc versions of these routines do this); if you
+use a private malloc implementation that does not set
+.IR errno ,
+then certain library routines may fail without having
+a reason in
 .IR errno .
-Private memory allocators may also need to replace other glibc functions;
-see "Replacing malloc" in the glibc manual for details.
 .PP
-Crashes in memory allocators
+Crashes in
+.BR malloc (),
+.BR calloc (),
+.BR realloc (),
+or
+.BR free ()
 are almost always related to heap corruption, such as overflowing
 an allocated chunk or freeing the same pointer twice.
 .PP
@@ -373,28 +378,19 @@ implementation is tunable via environment variables; see
 for details.
 .SS Nonportable behavior
 The behavior of
-these functions when the requested size is zero
+.BR realloc ()
+when
+.I size
+is equal to zero,
+and
+.I ptr
+is not NULL,
 is glibc specific;
-other implementations may return NULL without setting
-.IR errno ,
-and portable POSIX programs should tolerate such behavior.
+other implementations may return NULL, and set
+.IR errno .
+Portable POSIX programs should avoid it.
 See
 .BR realloc (3p).
-.PP
-POSIX requires memory allocators
-to set
-.I errno
-upon failure.
-However, the C standard does not require this, and applications
-portable to non-POSIX platforms should not assume this.
-.PP
-Portable programs should not use private memory allocators,
-as POSIX and the C standard do not allow replacement of
-.BR malloc (),
-.BR free (),
-.BR calloc (),
-and
-.BR realloc ().
 .SH SEE ALSO
 .\" http://g.oswego.edu/dl/html/malloc.html
 .\" A Memory Allocator - by Doug Lea

man3/malloc_hook.3

@@ -11,7 +11,7 @@
 .SH NAME
 __malloc_hook, __malloc_initialize_hook,
 __memalign_hook, __free_hook, __realloc_hook,
-__after_morecore_hook \- malloc debugging variables (DEPRECATED)
+__after_morecore_hook \- malloc debugging variables
 .SH SYNOPSIS
 .nf
 .B "#include <malloc.h>"
@@ -86,18 +86,11 @@ The use of these hook functions is not safe in multithreaded programs,
 and they are now deprecated.
 From glibc 2.24 onwards, the
 .B __malloc_initialize_hook
-variable has been removed from the API,
-and from glibc 2.34 onwards, all
-the hook variables have been removed from the API.
+variable has been removed from the API.
 .\" https://bugzilla.redhat.com/show_bug.cgi?id=450187
 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=9957
 Programmers should instead preempt calls to the relevant functions
-by defining and exporting
-.BR malloc (),
-.BR free (),
-.BR realloc (),
-and
-.BR calloc ().
+by defining and exporting functions such as "malloc" and "free".
 .SH EXAMPLES
 Here is a short example of how to use these variables.
 .PP