diff options
Diffstat (limited to 'manual')
| -rw-r--r-- | manual/filesys.texi | 10 | ||||
| -rw-r--r-- | manual/memory.texi | 7 |
2 files changed, 12 insertions, 5 deletions
diff --git a/manual/filesys.texi b/manual/filesys.texi index 8a91639a4e..c5c2f105d2 100644 --- a/manual/filesys.texi +++ b/manual/filesys.texi @@ -485,8 +485,8 @@ The @code{alphasort} function behaves like the @code{strcoll} function are not string pointers but instead they are of type @code{struct dirent **}. -Return value of is less than, equal to, or greater than zero depending -on the order of the two entries @var{a} and @var{b}. +Return value of @code{alphasort} is less than, equal to, or greater than +zero depending on the order of the two entries @var{a} and @var{b}. @end deftypefun @comment dirent.h @@ -509,7 +509,7 @@ only that the directory entries it returns are described by elements of type @w{@code{struct dirent64}}. The function pointed to by @var{selector} is again used to select the wanted entries only that @var{selector} now must point to a function which takes a -@w{@code{struct dirent64 *} parameter. +@w{@code{struct dirent64 *}} parameter. The @var{cmp} now must be a function which expects its two arguments to be of type @code{struct dirent64 **}. @@ -528,8 +528,8 @@ The @code{alphasort64} function behaves like the @code{strcoll} function are not string pointers but instead they are of type @code{struct dirent64 **}. -Return value of is less than, equal to, or greater than zero depending -on the order of the two entries @var{a} and @var{b}. +Return value of @code{alphasort64} is less than, equal to, or greater +than zero depending on the order of the two entries @var{a} and @var{b}. @end deftypefun @comment dirent.h diff --git a/manual/memory.texi b/manual/memory.texi index 09147bcd14..262d772fc6 100644 --- a/manual/memory.texi +++ b/manual/memory.texi @@ -625,6 +625,13 @@ immediately. This can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down. +So, what's the difference between using @code{MALLOC_CHECK_} and linking +with @samp{-lmcheck}? @code{MALLOC_CHECK_} is orthognal with respect to +@samp{-lmcheck}. @samp{-lmcheck} has been added for backward +compatibility. Both @code{MALLOC_CHECK_} and @samp{-lmcheck} should +uncover the same bugs - but using @code{MALLOC_CHECK_} you don't need to +recompile your application. + @node Hooks for Malloc @subsection Storage Allocation Hooks @cindex allocation hooks, for @code{malloc} |