another documentation bug

[Peter Jay Salzman]

hi guys,

i'm on sarge (glibc 2.3.1).  according to the libc info page:

   If `MALLOC_CHECK_' is set to `0', any detected heap corruption is
   silently ignored; if set to `1', a diagnostic is printed on `stderr';
   if set to `2', `abort' is called 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.

i think this paragraph needs the following sentence:

   If `MALLOC_CHECK_' is set to `3', any detected heap corruption causes
   the combined effects of `1' and `2', that is, a diagnostic message is
   printed on `stderr' and `abort' is called immediately.

i'm not on the mailing list, so please cc: me if there are any
questions.

thanks!
pete

-- 
GPG Instructions: http://www.dirac.org/linux/gpg
GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D

pgpsPRBF5vBIz.pgp
Description: PGP signature