Bug 787737

Summary: internal compiler error: Segmentation fault (program cc1)
Product: [Fedora] Fedora Reporter: nucleo <alekcejk>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: jakub, kevin, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gcc-4.6.3-2.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-22 01:57:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
fidlib.c preprocessed output none

Description nucleo 2012-02-06 16:04:23 UTC 
Description of problem:
Compiler crashes when I trying to build qutecom
http://nucleo.fedorapeople.org/rpms/qutecom/qutecom-2.2.1-1.fc16.src.rpm

Version-Release number of selected component (if applicable):
gcc-4.6.2-1.fc16.i686

Actual results:
{standard input}: Assembler messages:
{standard input}:13711: Warning: end of file not at end of a line; newline inserted
{standard input}:14581: Error: unbalanced parenthesis in operand 1.
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
gcc: internal compiler error: Segmentation fault (program cc1)


Additional info:
When Fedora 16 was just installed this package built without errors but now compiler crashes.
Comment 1 Rex Dieter 2012-02-06 16:12:10 UTC 
cd /home/rdieter1/pkgs.fedoraproject.org/work/qutecom/qutecom-2.2.1/x86_64-redhat-linux-gnu/wifo/phapi/fidlib && /usr/lib64/ccache/gcc  -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4  -m64 -mtune=generic  -Wmissing-prototypes -O3 -DNDEBUG -I/home/rdieter1/pkgs.fedoraproject.org/work/qutecom/qutecom-2.2.1/wifo/phapi/fidlib/include    -fPIC -Wall -Wstrict-aliasing -Wextra -Wno-unused-parameter -fmessage-length=0 -o CMakeFiles/fidlib.dir/src/fidlib.o   -c /home/rdieter1/pkgs.fedoraproject.org/work/qutecom/qutecom-2.2.1/wifo/phapi/fidlib/src/fidlib.c
Comment 2 Rex Dieter 2012-02-06 16:13:23 UTC 
Created attachment 559677 [details]
fidlib.c preprocessed output
Comment 3 Kevin Kofler 2012-02-06 19:29:38 UTC 
I think a stack backtrace of the segfault would also be helpful.
Comment 4 Rex Dieter 2012-02-06 19:57:45 UTC 
*** Bug 787814 has been marked as a duplicate of this bug. ***
Comment 5 Rex Dieter 2012-02-06 19:58:13 UTC 
See abrt data in bug #787814 (including backtrace)
Comment 6 nucleo 2012-02-10 19:00:56 UTC 
Bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51077 marked as fixed.
Is something else needs fixes for fixing this segmentation fault?
Comment 7 nucleo 2012-02-22 02:35:38 UTC 
So, if bug fixed in upstream why it can't be fixed here?
Comment 8 Fedora Update System 2012-03-06 21:17:49 UTC 
gcc-4.6.3-2.fc16,libtool-2.4-9.fc16,gcc-python-plugin-0.9-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/gcc-4.6.3-2.fc16,libtool-2.4-9.fc16,gcc-python-plugin-0.9-1.fc16
Comment 9 Fedora Update System 2012-03-08 04:56:31 UTC 
Package gcc-4.6.3-2.fc16, libtool-2.4-9.fc16, gcc-python-plugin-0.9-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gcc-4.6.3-2.fc16 libtool-2.4-9.fc16 gcc-python-plugin-0.9-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-3370/gcc-4.6.3-2.fc16,libtool-2.4-9.fc16,gcc-python-plugin-0.9-1.fc16
then log in and leave karma (feedback).
Comment 10 Fedora Update System 2012-03-22 01:57:55 UTC 
gcc-4.6.3-2.fc16, libtool-2.4-9.fc16, gcc-python-plugin-0.9-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.