public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Borden <jborden@sorenson.com>
To: gcc-gnats@gcc.gnu.org
Subject: c/7502: internal error: Segmentation fault
Date: Mon, 05 Aug 2002 16:26:00 -0000 [thread overview]
Message-ID: <20020805231741.28029.qmail@sources.redhat.com> (raw)
>Number: 7502
>Category: c
>Synopsis: internal error: Segmentation fault
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Aug 05 16:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Jason Borden <jborden@sorenson.com>
>Release: unknown-1.0
>Organization:
>Environment:
Redhat 7.3 Linux (intel)
AMD Athlon XP 2000+
VIA KT266A chipset motherboard
512 MB memory
75 GB hard disk
Same problem with gcc 2.96rh, 3.1.1, and current CVS
>Description:
My system almost seems cursed! Please note that about 95% of the files that I compile, do compile correctly, the remaining 5% get: the internal error: Segmentation fault, always on the same files with the same configuration, therefore, I don't beleive it to be a problem with my computer. However the problem can be fixed usually by changing compilation options, for instance, by changing a -O99 or -O3 to an -O2 or -O, it will sometimes compile correctly. Also adding a -fomit-frame-pointer, removing -Wall, or doing a -E to preprocess and then a -x cpp-output, will sometimes fix the problem. I've tried several different compiler builds including 2.96rh, 3.1.1, and the CVS builds, all have the same problem. I can compile with the same compilers on my pentium-mmx laptop and pentium 4 without having any problems, which leads me to beleive that the problem exists with the athlon-xp or kt266a combination, or both? I have tried running both the linux 2.4.18 and 2.4.19 kernels, changing the ulimit on my stack size to unlimited, and tons of other compiler tweaks, without being able to get it to make a difference. I have attached some examples of the problem just from compiling glibc-2.2.5, the problem has also occurred in compiling several other projects. Please let me know if you can get this to reproduce elsewhere, before I go crazy! Thanks, Jason
>How-To-Repeat:
Try it with the same hardware configuration if possible
>Fix:
No definite fixes that I know of beyond changing compiling options (pain in the rear for a lot of projects)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="gcc.bugs"
Content-Disposition: inline; filename="gcc.bugs"
gcc wcstod_l.c -c -O3 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -m3dnow -march=athlon-xp -mcpu=athlon-xp -mmmx -msse -g -I../stdlib -I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/include -isystem /usr/src/linux-2.4.19/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -o wcstod_l.og
../stdlib/strtod.c: In function `round_and_return':
../stdlib/strtod.c:1576: internal error: Segmentation fault
gcc regex.c -c -O3 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -m3dnow -march=athlon-xp -mcpu=athlon-xp -mmmx -msse -fomit-frame-pointer -g0 -O99 -fomit-frame-pointer -D__USE_STRING_INLINES -Wno-strict-prototypes -DMBS_SUPPORT -I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/include -isystem /usr/src/linux-2.4.19/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -o regex.o
In file included from ../include/regex.h:2,
from regex.c:191:
../posix/regex.h:535:1: warning: "__restrict_arr" redefined
In file included from ../include/sys/cdefs.h:1,
from ../include/features.h:283,
from ../posix/sys/types.h:26,
from ../include/sys/types.h:1,
from regex.c:49:
../misc/sys/cdefs.h:212:1: warning: this is the location of the previous definition
In file included from regex.c:631:
regex.c: In function `findidx':
regex.c:6533: internal error: Segmentation fault
gcc ../sysdeps/generic/segfault.c -c -O3 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -m3dnow -march=athlon-xp -mcpu=athlon-xp -mmmx -msse -fomit-frame-pointer -fPIC -g0 -O99 -fomit-frame-pointer -D__USE_STRING_INLINES -I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/include -isystem /usr/src/linux-2.4.19/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -DSHARED -o segfault.os
../sysdeps/generic/segfault.c: In function `register_dump':
../sysdeps/generic/segfault.c:99: internal error: Segmentation fault
next reply other threads:[~2002-08-05 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 16:26 Jason Borden [this message]
2002-08-05 22:56 Jason Borden
2002-08-25 4:01 paolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020805231741.28029.qmail@sources.redhat.com \
--to=jborden@sorenson.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).