Bug 712406

Summary: deadlock in malloc()
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0CC: 04mvs89, ajax, fweimer, jwest, mfranc, moshiro, nakano.hiroaki, nmurray, patrickm, pm-eus, pmuller, schwab, tmuneda, wcohen
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.12-1.7.el6_0.8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-18 08:49:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 676591    
Bug Blocks:    

Description RHEL Program Management 2011-06-10 13:40:07 UTC
This bug has been copied from bug #676591 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 5 Andreas Schwab 2011-07-08 06:32:48 UTC
You need to link against libgcc_s.

Comment 6 Miroslav Franc 2011-07-08 07:21:02 UTC
(In reply to comment #5)
> You need to link against libgcc_s.

I was under impression this is for C++ only. That's why g++ links against it by default while gcc doesn't. But 1/ it shouldn't matter and 2/ even with -lgcc_s I'm getting deadlock and the same backtrace.

Comment 7 Andreas Schwab 2011-07-08 10:18:25 UTC
This is simply undefined behaviour.

Comment 15 Andreas Schwab 2011-07-12 11:52:58 UTC
A program committing suicide by deliberately overwriting the heap is not a test case.

Comment 16 Andreas Schwab 2011-07-13 08:25:46 UTC
The current behaviour is deliberate and has served well for the last 20 years without anyone noticing.  There is nothing more to fix.

Comment 20 errata-xmlrpc 2011-08-18 08:49:28 UTC
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 therefore 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/RHBA-2011-1180.html