Bug 1265333

Summary:	Regression in glibc-2.12-1.166.el6_7.3
Product:	Red Hat Enterprise Linux 6	Reporter:	Steve Snyder <swsnyder>
Component:	glibc	Assignee:	Carlos O'Donell <codonell>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-tools-bugs
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	ashankar, fweimer, mnewsome, pfrankli
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-22 17:56:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.