Bug 455355

Summary: malloc debugging is noisy, messes up uname output
Product: [Fedora] Fedora Reporter: Kevin Kofler <kevin>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: drepper, fweimer, kirbyzhou, notting, rdieter, xgoran
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.8.90-9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-20 08:58:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin Kofler 2008-07-15 00:41:55 UTC 
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 cmake.org 
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):
glibc-2.8.90-8
initscripts-8.79-1.fc10

How reproducible:
Always

Steps to Reproduce:
1. Try running a build with the latest glibc and initscripts.
  
Actual results:
build.log gets spammed with "malloc: using debugging hooks", cmake gets 
confused and errors.

Expected results:
Use of debugging hooks is silent.

Additional info:
See also http://fedorahosted.org/rel-eng/ticket/733
Comment 1 Ulrich Drepper 2008-07-20 08:58:10 UTC 
Changed in 2.8.90-9.
Comment 2 Kirby Zhou 2009-10-08 15:26:39 UTC 
The same problem is in RHEL-5
Comment 3 Goran P 2011-05-19 12:45:44 UTC 
Debugging hooks is ON.
check: echo $MALLOC_CHECK_
It is probably in 1. To solve your problem, enter: export MALLOC_CHECK_=0