Seg Faults with gcc 2.8.1 !!

Seg Faults with gcc 2.8.1 !!

Post by Kertis A. Henderso » Tue, 19 May 1998 04:00:00



I run RedHat 5.0 and I just got gcc 2.8.1, because I couldn't compile
anything large with the old 2.7.2.2 that I had.  I compiled my kernel
(2.0.33) with this version of gcc.  Now, when I run isapnp, or X, I get
a seg fault, and a core file.  (I hate core files.)

Is this a problem with gcc?  Should I upgrade libc, too?  I seem to have
version 2.0.7.

--

Kertis Henderson

 
 
 

Seg Faults with gcc 2.8.1 !!

Post by Peter Whysal » Thu, 21 May 1998 04:00:00



> I run RedHat 5.0 and I just got gcc 2.8.1, because I couldn't compile
> anything large with the old 2.7.2.2 that I had.  I compiled my kernel
> (2.0.33) with this version of gcc.  Now, when I run isapnp, or X, I get
> a seg fault, and a core file.  (I hate core files.)

> Is this a problem with gcc?  Should I upgrade libc, too?  I seem to have
> version 2.0.7.

Why couldn't you compile anything large with 2.7.2? I have that version
and it cheerfully compiled a 2.0.30 kernel, xemacs 19.14 (now that is a
large source tree), glibc2.0.6 (another very large source tree), the
Gimp and so on and so forth. All big things. I suspect (but I don't
know) that 2.8.1 is still experimental and you can't rely on it. AFAIK
2.7.2 is a stable release.

Maybe it's not gcc at all? I can't see what gcc would have to do with
segfaults when you start X EXCEPT if you replaced the C libraries.
Examine your setup. Make sure you have the libraries your apps are
expecting.

Peter.
--
Peter Whysall                     | Do not dabble in the affairs
peter.whysall_at_tad-centre.co.uk | of dragons, for you are crunchy
URL: http://www.tad-centre.co.uk  | when dipped in chocolate
IT Coordinator                    | -- ANON

 
 
 

Seg Faults with gcc 2.8.1 !!

Post by John Summerfie » Fri, 22 May 1998 04:00:00



: I run RedHat 5.0 and I just got gcc 2.8.1, because I couldn't compile
: anything large with the old 2.7.2.2 that I had.  I compiled my kernel
: (2.0.33) with this version of gcc.  Now, when I run isapnp, or X, I get
: a seg fault, and a core file.  (I hate core files.)

2.7.2.3 is recommended for kernel 2.1.99. Reports of 2.8 are that it's buggy and
not to be used unless you really need its new features.

: Is this a problem with gcc?  Should I upgrade libc, too?  I seem to have
: version 2.0.7.

libc 5.4.44 is recommend for 2.1.99 kernel. The latest glibc i know of is glibc-2.0.7-7.

afaik these are regarded as stable.

btw It's possible to hve libc5 and libc6 (glibc) coexist.

--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.

 
 
 

1. help!! seg fault with gcc

When I try to compile anything with
gcc, the executable invariably causes
segmentation fault -- core dumped.
Even helloworld.c does this!
I'm running debian linux 2.0.6, and gcc
has been running fine before (I think, though
I'm not sure if I'd used it since I recompiled
the kernel).  I'm fairly green so any suggestions
are welcome.


thanks!

chris

Summary:
Keywords:

2. "mirroring" with or without SVM

3. Intermittent seg faults - elf, xview or gcc (or all three)

4. gcc floating point

5. seg faults when compiling gcc with -pipe

6. alsa-driver-0.9.0rc3 breaks!

7. suddenly Seg Faults on exit of gcc-compiled bins, and on gnu Make's

8. touch panel device driver

9. Change from gcc to egcs gives seg fault in make

10. gcc Error 139 or Seg fault (glibc2.0.7)

11. [Fwd: gcc seg fault when not casting pointers properly ???]

12. gcc-2.7.2 seg faults

13. printf(""); preventing gcc seg faults?!?!?!?!?