Bug 211614 - Gcc 4.1.1 segmentation faults when compiling various things
Summary: Gcc 4.1.1 segmentation faults when compiling various things
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc   
(Show other bugs)
Version: 6
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-20 14:15 UTC by Jonathan Paul Cowherd
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-21 15:14:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Bzip2 tar file of the /tmp/cc<hash>.out files from compiling things (304.30 KB, application/octet-stream)
2006-10-20 14:15 UTC, Jonathan Paul Cowherd
no flags Details

Description Jonathan Paul Cowherd 2006-10-20 14:15:40 UTC
Description of problem:

When attempting to re-compile any existing product that compiled under Fedora
Core 6 (test 4/pre-final), things would compile to completion without error. 
Now when attempting to compile things like running "make menuconfig" on the
kernel, mplayer, or NVidia's kernel module (I know you guys don't support it,
I'm just addding it FYI), there is an internal compiler error which looks like a
segmentation fault.  I've ran strace on it, but I don't understand what I'm not
familiar enough to know exactly what is going it.  It seems that there is
something that occurs with a memory copy or allocation.

Version-Release number of selected component (if applicable):

Kernel 2.6.18-2798-1.fc6
Gcc version 4.1.1
Glibc version 2.5-3

How reproducible:

Very reproducible.  Got a confirmation post from Steve Grubb (sgrubb@redhat.com)
that he is seeing something similar.

Steps to Reproduce:
1.  Make sure the versions of code are installed above on x86_64 machine.
2.  cd to /usr/src/kernels/2.6.18-1.2798.fc6-x86_64 (have kernel-devel installed)
3.  make menuconfig
Actual results:

[root@jaguar 2.6.18-1.2798.fc6-x86_64]# make menuconfig
  HOSTCC  scripts/kconfig/conf.o
scripts/kconfig/conf.c: In function âstripâ:
scripts/kconfig/conf.c:58: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/cc603YAn.out file, please attach this to
your bugreport.
make[1]: *** [scripts/kconfig/conf.o] Error 1
make: *** [menuconfig] Error 2

Expected results:

Entered the menuconfig curses screeen.

Additional info:

So I used the kernel as an example, but it occurs with other programs that would
compile before but not now:  Nvidia driver and mplayer are the two example
/tmp/cc<hash>.out files that I've included.

Comment 1 Jonathan Paul Cowherd 2006-10-20 14:15:41 UTC
Created attachment 138973 [details]
Bzip2 tar file of the /tmp/cc<hash>.out files from compiling things

Comment 2 Jakub Jelinek 2006-10-20 14:33:40 UTC
Can't reproduce this with gcc-4.1.1-30 nor any other gcc I have around.
On your box, is there anything gcc doesn't segfault on?  Some of the dumps
are really trivial one liners, if the bug was in gcc, it wouldn't definitely
pass its tens thousands of tests run during the build.
So, I'd say either you have hardware problems, or some kernel bug.

Comment 3 Jonathan Paul Cowherd 2006-10-20 15:02:10 UTC
I created a simple make file and c program to show that the basics work:

#include <stdio.h>

int main() {
        printf("Hello World\n");

# Make file for Hello.c

        $(CC) $(CFLAGS) -o hello.o hello.c

        rm hello.o

I'll try a diagnostic CD to see if something is going bad with my processor,
memory, or drives.  If you have any other tests that I could try that may help
pinpoint this issue, let me know.

Comment 4 Michal Jaegermann 2006-10-20 17:07:47 UTC
There is another report of similar problems and that is even on
another architecture.  See:


Unfortunately this note is also remarkably short on essential details;
in particular it also does not mention what _really_ bombs out.

Some guesses about possibly reasons based on past experiences:
  - out of space on /tmp
  - something messed up in a file system used by /tmp
  - gcc optimizer spooked by something (not necessarily easy to
Still I did not run into gcc exceptions for reasons like above for
quite a while now.

Comment 5 Jonathan Paul Cowherd 2006-10-21 15:14:57 UTC
Looks like I'm having hardware problems.  Used two different cpu stress tests
from ubcd 3.4 and both came up with errors.  Popped my case open and found that
a fan had stopped working, so I'll be buying a new MB and CPU soon.

Thanks for your time.


Note You need to log in before you can comment on or make changes to this bug.