Bug 1251488

Summary: gcov crash if two(or more) forks happen at the same time
Product: Red Hat Enterprise Linux 6 Reporter: Codrut Grosu <gc_chris>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Michael Petlan <mpetlan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6CC: gc_chris, jspahr, law, mcermak, mnewsome, mpetlan, mpolacek, ohudlick
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: gcc-4.4.7-17.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 21:41:39 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:    
Bug Blocks: 1172231, 1271375    

Description Codrut Grosu 2015-08-07 13:21:20 UTC
Hello,

I'm a CentOS 6.6 user and I'm using the default GCC (4.4.7) compiler of CentOS 6.6.

I'm trying to use the gcov tool for my code in CentOS 6.6 with gcc 4.4.7 and I have the same problem that was reported at [1].

I send an email to Richard Biener to fix the bug for the gcc 4.4.7 but he told me that gcc 4.4.7 is no longer maintained.

The bug was fixed for gcc 4.8.0 and above .

He also added that I should "talk with the boys from RedHat to backport the patch to their compiler".

I hope that you boys can do your magic again and fix this bug.

The fact that CentOS 6 will be maintained until 2020 gives me confidence that you'll do your best to fix this bug.

I'm puting this bug here because on https://www.centos.org/forums they told me to report the bug to RedHat on bugzilla.redhat.com .

[1] : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49484 [^]



Thanks,
Codrut Grosu.

P.S. Sorry for my English... I'm better with vim :D :P

Comment 5 Michael Petlan 2016-01-14 13:52:21 UTC
Reproduced with:  4.4.7-16.el6
Verified against: 4.4.7-17.el6

Comment 7 errata-xmlrpc 2016-05-10 21:41:39 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-0849.html