Red Hat Bugzilla – Bug 455355
malloc debugging is noisy, messes up uname output
Last modified: 2016-11-24 10:47:18 EST
Description of problem:
When malloc debugging is enabled, which the latest initscripts-8.79-1.fc10
does system-wide, glibc prints a message to stderr (or is it stdout?) for
every single program starting up:
malloc: using debugging hooks
That breaks programs like uname, at least cmake gets confused by the uname
output and prints:
System is unknown to cmake, create:
Platform/malloc: using debugging hooks
Linux to use this system, please send your config file to email@example.com
so it can be added to cmake
and errors, breaking KDE package builds. If debugging is to be enabled
system-wide in Rawhide, it has to be silent unless/until an error occurs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try running a build with the latest glibc and initscripts.
build.log gets spammed with "malloc: using debugging hooks", cmake gets
confused and errors.
Use of debugging hooks is silent.
See also http://fedorahosted.org/rel-eng/ticket/733
Changed in 2.8.90-9.
The same problem is in RHEL-5
Debugging hooks is ON.
check: echo $MALLOC_CHECK_
It is probably in 1. To solve your problem, enter: export MALLOC_CHECK_=0