Bug 77804
Summary: | gcc: Internal error: Segmentation fault (program as) | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <hahnsang.kim> |
Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-02 20:40:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-11-13 21:08:06 UTC
Cannot reproduce it. Furthermore, from your error message it is gas, not gcc which segfaults, so you'd need attach assembly which as is segfaulting on (reproduceably). I hardly understand your comment. Then what is your suggestion or your solution? What does it mean by "attach assebly"? by the way, the following tells me that internal error happened in gcc, doesn't it? ++ [garros@ip6 ip6test]$ gcc gethostbyname2.c gcc: Internal error: Segmentation fault (program as) Please submit a full bug report. See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions. [garros@ip6 ip6test]$ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit Thread model: posix gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) I have also been unable to reproduce this problem with the source code you provided. You might want to run a thorough stress test on your system to ensure it is not hardware related. Many gcc faults can be credited to quirky hardware. "memtest86" is a good start - http://www.memtest86.com It tells you program as segfaulted and thus gcc driver couldn't build the program. By attaching assembly I mean that you do: gcc -S gethostbyname2.c and attach gethostbyname2.s it creates, provided that running as -o gethostbyname2.o gethostbyname2.s segfaults reproduceably. If not, it is most probably hardware problem. No feedback, closing. |