aboutsummaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-03-23 11:53:10 +0000
committerUlrich Drepper <drepper@redhat.com>1998-03-23 11:53:10 +0000
commit789b13c4e808dfcdd58d52bc5f4221047fee57e5 (patch)
tree535adca7a43ba39ce0eb18c0c74d0517594d9b8c /manual
parent9a24f9061c4e5e567350734bfb6a2aaa4e2106dc (diff)
downloadglibc-789b13c4e808dfcdd58d52bc5f4221047fee57e5.tar
glibc-789b13c4e808dfcdd58d52bc5f4221047fee57e5.tar.gz
glibc-789b13c4e808dfcdd58d52bc5f4221047fee57e5.tar.bz2
glibc-789b13c4e808dfcdd58d52bc5f4221047fee57e5.zip
Update.
1998-03-23 07:52 H.J. Lu <hjl@gnu.org> * elf/dl-close.c (_dl_close): Fix byte count while removing the shared object from the global scope list and optimize a little bit. 1998-03-22 Andreas Jaeger <aj@arthur.rhein-neckar.de> * manual/filesys.texi (Scanning Directory Content): Add missing closing brace. (Scanning Directory Content): Fix text. 1998-03-22 Andreas Jaeger <aj@arthur.rhein-neckar.de> * manual/memory.texi (Heap Consistency Checking): Add paragraph explaining difference of -lmcheck and MALLOC_CHECK_. 1998-03-23 Andreas Jaeger <aj@arthur.rhein-neckar.de> * sysdeps/unix/sysv/linux/fstatvfs.c (fstatvfs): Correct some typos in comments. 1998-03-20 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * test-skeleton.c (main): Fix test for exit signal. 1998-03-22 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * sysdeps/generic/strtok_r.c: Undefine __strtok_r. 1998-03-22 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * sysdeps/generic/memcmp.c [_LIBC]: Define WORDS_BIGENDIAN as appropriate. 1998-03-23 11:14 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * libc.map: Export __strtok_r. 1998-03-23 Ulrich Drepper <drepper@cygnus.com> * posix/regex.c (re_compile_fastmap): Remove unused variable num_regs and adjust comment. Patch by Jim Meyering <meyering@ascend.com>. * math/math.h (M_*l): Extend long double constants to be usable for 128 bit floats. Patch by Richard Henderson. 1998-03-23 11:16 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> Patch by Tim Waugh and Andreas Schwab.
Diffstat (limited to 'manual')
-rw-r--r--manual/filesys.texi10
-rw-r--r--manual/memory.texi7
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}