Bug 149205
Summary: | malloc: top chunk is corrupt w/ MALLOC_CHECK_=3 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | jordan hargrave <jordan_hargrave> | ||||
Component: | glibc | Assignee: | Jakub Jelinek <jakub> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | jturner, wwlinuxengineering | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-05-10 20:17:52 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: | |||||||
Attachments: |
|
Description
jordan hargrave
2005-02-21 03:00:18 UTC
Created attachment 111248 [details]
mtest.c - causes glibc error message if MALLOC_CHECK_=3 is set
glibc-2.3.3-53 is not what is shipped in RHEL4. With glibc-2.3.4-2 I can't reproduce this both on i686 and x86_64 running 32-bit program: MALLOC_CHECK_=3 ./mtest malloc: using debugging hooks .........................success: 5fec ALLOC_CHECK_=3 ./mtest malloc: using debugging hooks .................................success: 7fee Though I can reproduce it with glibc-2.3.2-95.30. Yeah, fixes this for RHEL3. Queued for RHEL3 U5. So appears this is a RHEL3 bug only . . . RHEL4 isn't affected, right? If that's the case, then I'll switch the product/version to be appropriate. A fixed RHEL3 glibc candidate at ftp://people.redhat.com/jakub/glibc/2.3.2-95.33/ This is fixed in RHEL3 U5 beta, glibc-2.3.2-95.33 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-256.html |