Please add a descriptive phrase to the summary, and more in-depth description here (be sure to note any arch-specific issues): Please pull in bug 133266.
*** Bug 133278 has been marked as a duplicate of this bug. ***
(For those people that lack the special X-ray vision glasses required to view bug 133266, it contains the following text:) The glibc in RHEL4 will perform more sanity checks internally in order to prevent and detect data corruption early. In case that you have a program from a third party ISV that triggers these corruption checks you should file a defect report with the vendor of this application since this indicates a really serious bug; however you can also chose to accept the data corruption and disable the checks by setting "MALLOC_CHECK_=0" in the environment. We should provide an example and show this: *** glibc detected *** double free or corruption: 0x0937d008 ***
Added; closing...