Bug 354131 - use MALLOC_CHECK_ (not _MALLOC_CHECK)
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-26 10:29 EDT by John Reiser
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-26 10:42:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Reiser 2007-10-26 10:29:45 EDT
Description of problem: The environment variable that triggers the extra
checking inside malloc/free/realloc by glibc is spelled MALLOC_CHECK_ with a
trailing underscore, not _MALLOC_CHECK with a leading underscore.  All the
execve from anaconda specify the wrong one.

Version-Release number of selected component (if applicable):

How reproducible: always

Steps to Reproduce:
1. as soon as vtty2 is available:
strace -v -e trace=execve -s 400 -p <pid-of-anaconda>
(supply 'strace' on a USB flash memory device before boot, and mount the device
2. look at the environment variables in execve().
Actual results:
735   execve("/usr/bin/loadkeys", ["/usr/bin/loadkeys"..., "us"...],

Expected results: "MALLOC_CHECK_=2"

Additional info: The spelling is listed as MALLOC_CHECK_ (with a trailing
underscore) in "man 3 malloc", and in "info libc".  The code is in
glibc/malloc/arena.c, function ptmnalloc_init(), around line 559 in glibc-2.7-2.
Comment 1 Chris Lumens 2007-10-26 10:42:59 EDT
Thanks, this will be fixed in the next build of anaconda.

Note You need to log in before you can comment on or make changes to this bug.