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):
anaconda-11.3.0.45-1


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
yourself.)
2. look at the environment variables in execve().
3.
  
Actual results:
735   execve("/usr/bin/loadkeys", ["/usr/bin/loadkeys"..., "us"...],
["PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/mnt/sysimage/usr/X11R6/bin:/sbin:/usr/sbin"...,
"_MALLOC_CHECK=2"..., "MALLOC_PERTURB_=204"...,

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.