Bug 1276633

Summary: glibc: hide backtrace from tst-malloc-backtrace
Product: Red Hat Enterprise Linux 6 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: Florian Weimer <fweimer>
Status: CLOSED ERRATA QA Contact: Arjun Shankar <ashankar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: ashankar, codonell, fweimer, mcermak, mnewsome, pfrankli, qe-baseos-tools-bugs
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.12-1.175.el6 Doc Type: Bug Fix
Doc Text:
At build time, a misleading error message during a malloc test is no longer printed.
 Story Points: ---
Clone Of: 1276631 Environment:
Last Closed: 2016-05-10 21:28:22 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:
Bug Depends On: 1276631    
Bug Blocks:    

Description Florian Weimer 2015-10-30 10:36:23 UTC 
+++ This bug was initially created as a clone of Bug #1276631 +++

We should backport this upstream commit:

https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=02242448bf431a69fd0b8c929ca4408a05479baa

Without this, messages such as the one below will appear in build logs.  The point of this test is to generate a backtrace and ensure it is printed successfully, so the backtrace as such is entirely expected.  It is just confusing that it appears in build logs.

*** Error in `/builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/malloc/tst-malloc-backtrace': malloc(): memory corruption: 0x000002aaaaae0010 ***
======= Backtrace: =========
/builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/libc.so.6(+0x7bd88)[0x3ffb7eebd88]
/builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/libc.so.6(__libc_malloc+0x58)[0x3ffb7eed080]
/builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/malloc/tst-malloc-backtrace[0x401604]
======= Memory map: ========
00400000-00410000 r-xp 00000000 08:05 5398005                            /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/malloc/tst-malloc-backtrace
00410000-00420000 r--p 00000000 08:05 5398005                            /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/malloc/tst-malloc-backtrace
00420000-00430000 rw-p 00010000 08:05 5398005                            /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/malloc/tst-malloc-backtrace
2aaaaaa0000-2aaaaac0000 r-xp 00000000 08:05 5390292                      /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/elf/ld.so
2aaaaac0000-2aaaaad0000 r--p 00010000 08:05 5390292                      /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/elf/ld.so
2aaaaad0000-2aaaaae0000 rw-p 00020000 08:05 5390292                      /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/elf/ld.so
2aaaaae0000-2aaaab10000 rw-p 00000000 00:00 0                            [heap]
3ffb0000000-3ffb0030000 rw-p 00000000 00:00 0 
3ffb0030000-3ffb4000000 ---p 00000000 00:00 0 
3ffb7e10000-3ffb7e30000 r-xp 00000000 08:05 4587843                      /usr/lib64/libgcc_s-4.8.5-20150702.so.1
3ffb7e30000-3ffb7e40000 r--p 00010000 08:05 4587843                      /usr/lib64/libgcc_s-4.8.5-20150702.so.1
3ffb7e40000-3ffb7e50000 rw-p 00020000 08:05 4587843                      /usr/lib64/libgcc_s-4.8.5-20150702.so.1
3ffb7e60000-3ffb7e70000 rw-p 00000000 00:00 0 
3ffb7e70000-3ffb7fd0000 r-xp 00000000 08:05 5390294                      /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/libc.so
3ffb7fd0000-3ffb7fe0000 r--p 00150000 08:05 5390294                      /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/libc.so
3ffb7fe0000-3ffb7ff0000 rw-p 00160000 08:05 5390294                      /builddir/build/BUILD/glibc-2.17-c758a686/build-aarch64-redhat-linux/libc.so
3ffb7ff0000-3ffb8000000 r--p 00000000 00:00 0                            [vvar]
3ffb8000000-3ffb8010000 r-xp 00000000 00:00 0                            [vdso]
3fffffd0000-40000000000 rw-p 00000000 00:00 0                            [stack]
Comment 7 errata-xmlrpc 2016-05-10 21:28:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0834.html