Bug 197705
Summary: | kernel reg. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | prashanth <munichlinux> |
Component: | kernel | Assignee: | Jason Baron <jbaron> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | anderson, jakub, jbaron, knoel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 13:24:32 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
prashanth
2006-07-05 17:19:03 UTC
i get the problem ** glibc detected *** corrupted double-linked list: 0x08ddd040 *** when i compile the kernel can you please provide the version of the componets involved? kernel version, glibc version? as well as the steps to reproduce. thanks. im using Redhat EL4, kernel version is 2.6.9-5.EL and the glib version is 2.4.7 The error message you see is not a bug in glibc, but in one of the programs executed during kernel build. You need to find out which one, if it is reproduceable and if so, run it under valgrind, ElectricFence or some similar memory management checking tool to see where the problem is. I believe in kernel makefiles you use make V=1 ... to see the exact commands that are executed. Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |