RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1265333 - Regression in glibc-2.12-1.166.el6_7.3
Summary: Regression in glibc-2.12-1.166.el6_7.3
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glibc
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 16:56 UTC by Steve Snyder
Modified: 2016-11-24 12:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-22 17:56:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Steve Snyder 2015-09-22 16:56:34 UTC 
Description of problem:

No faults seen in previous release, but release today (2.12-1.166.el6_7.3.src.rpm) complains of memory corruption

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

2.12-1.166.el6_7.3.src.rpm

How reproducible:

Always

Steps to Reproduce:
1.  Run "rpmbuild --rebuild glibc-2.12-1.166.el6_7.1.src.rpm" (previous released version of package) and note no problem seen.

2. Run "rpmbuild --rebuild glibc-2.12-1.166.el6_7.3.src.rpm" (current package) and note faults on memory corruption.


Actual results:

*** glibc detected *** /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace: malloc(): memory corruption: 0x00007f7453c05010 ***
======= Backtrace: =========
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so.6(+0x75f4e)[0x7f7452164f4e]
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so.6(+0x7a41a)[0x7f745216941a]
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so.6(__libc_malloc+0x5c)[0x7f7452169b1c]
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace[0x40118a]
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace[0x40144a]
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so.6(__libc_start_main+0xfd)[0x7f745210dd5d]
/home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace[0x400dc9]
======= Memory map: ========
00400000-00402000 r-xp 00000000 08:03 289178                             /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace
00601000-00602000 r--p 00001000 08:03 289178                             /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace
00602000-00603000 rw-p 00002000 08:03 289178                             /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/malloc/tst-malloc-backtrace
38e7a00000-38e7a16000 r-xp 00000000 08:01 1311216                        /lib64/libgcc_s-4.4.7-20120601.so.1
38e7a16000-38e7c15000 ---p 00016000 08:01 1311216                        /lib64/libgcc_s-4.4.7-20120601.so.1
38e7c15000-38e7c16000 rw-p 00015000 08:01 1311216                        /lib64/libgcc_s-4.4.7-20120601.so.1
7f744c000000-7f744c021000 rw-p 00000000 00:00 0
7f744c021000-7f7450000000 ---p 00000000 00:00 0
7f74520ec000-7f74520ed000 rw-p 00000000 00:00 0
7f74520ed000-7f74520ef000 rw-p 00000000 00:00 0
7f74520ef000-7f7452279000 r-xp 00000000 08:03 281103                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so
7f7452279000-7f7452479000 ---p 0018a000 08:03 281103                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so
7f7452479000-7f745247d000 r--p 0018a000 08:03 281103                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so
7f745247d000-7f745247e000 rw-p 0018e000 08:03 281103                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/libc.so
7f745247e000-7f7452485000 rw-p 00000000 00:00 0
7f7452485000-7f74524a5000 r-xp 00000000 08:03 281102                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/elf/ld.so
7f74526a4000-7f74526a5000 r--p 0001f000 08:03 281102                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/elf/ld.so
7f74526a5000-7f74526a6000 rw-p 00020000 08:03 281102                     /home/rpmbuild/rpmbuild/BUILD/glibc-2.12-2-gc4ccff1/build-x86_64-linuxnptl/elf/ld.so
7f74526a6000-7f74526a7000 rw-p 00000000 00:00 0
7f7453c05000-7f7453c27000 rw-p 00000000 00:00 0                          [heap]
7ffd67f72000-7ffd67f88000 rw-p 00000000 00:00 0                          [stack]
7ffd67ff7000-7ffd67ff8000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]


Expected results:

No errors seen during build.

Additional info:

This is a fully-updated RHEL 6.7 system.
Comment 1 Carlos O'Donell 2015-09-22 17:56:23 UTC 
This is expected. The test in question "tst-malloc-backtrace" purposely triggers a memory corruption in order to determine if the malloc backtrace bug is fixed. This test is behaving as expected.
Note You need to log in before you can comment on or make changes to this bug.