public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: j-waldby@pat7.com To: gcc-gnats@gcc.gnu.org Subject: c/2754: "Internal error: Segmentation fault" w/ minor syntax problem Date: Sun, 06 May 2001 19:46:00 -0000 [thread overview] Message-ID: <20010507024114.1358.qmail@sourceware.cygnus.com> (raw) >Number: 2754 >Category: c >Synopsis: "Internal error: Segmentation fault" w/ minor syntax problem >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun May 06 19:46:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: j-waldby@pat7.com >Release: gcc version 2.96 20000731 (Red Hat Linux 7.0) >Organization: >Environment: Linux vyri.jiw 2.2.16-22 #2 Sat Apr 21 14:26:48 CDT 2001 i586 unknown gcc version 2.96 20000731 (Red Hat Linux 7.0) 266 MHz Pentium II 324MB >Description: gcc of attached star2-bug.c produces segfault on my RH7.0 system "Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.0)" (On my RH7.1 sys with similar compiler, ie, "Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-75)" it doesn't segfault, but instead says: star2-bug.c:1: invalid type argument of `unary *' star2-bug.c:2: confused by earlier errors, bailing out ) Here is star2-bug.c typedef char P[*2]; typedef struct D { P *op; } E; int main() {} Here is output of gcc -v -save-temps star2-bug.c : Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.0) /usr/lib/gcc-lib/i386-redhat-linux/2.96/cpp0 -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=96 -D__GNUC_PATCHLEVEL__=0 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem(posix) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__tune_i386__ star2-bug.c star2-bug.i GNU CPP version 2.96 20000731 (Red Hat Linux 7.0) (cpplib) (i386 Linux/ELF) ignoring nonexistent directory "/usr/i386-redhat-linux/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include /usr/lib/gcc-lib/i386-redhat-linux/2.96/include /usr/include End of search list. /usr/lib/gcc-lib/i386-redhat-linux/2.96/cc1 star2-bug.i -quiet -dumpbase star2-bug.c -version -o star2-bug.s GNU C version 2.96 20000731 (Red Hat Linux 7.0) (i386-redhat-linux) compiled by GNU C version 2.96 20000731 (Red Hat Linux 7.0). star2-bug.c:1: invalid type argument of `unary *' star2-bug.c:2: Internal error: Segmentation fault. Please submit a full bug report. See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. Here is star2-bug.i: # 1 "star2-bug.c" typedef char P[*2]; typedef struct D { P *op; } E; int main() {} Here is star2-bug.s: .file "star2-bug.c" .version "01.01" gcc2_compiled.: >How-To-Repeat: gcc the following on my RedHat 7.0 / linux 2.2.16 / gcc 2.96 20000731 system... typedef char P[*2]; typedef struct D { P *op; } E; int main() {} >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="star2-bug.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="star2-bug.c" dHlwZWRlZiBjaGFyIFBbKjJdOwp0eXBlZGVmIHN0cnVjdCBEIHsgIFAgKm9wOyB9IEU7CmludCBt YWluKCkge30K
reply other threads:[~2001-05-06 19:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010507024114.1358.qmail@sourceware.cygnus.com \ --to=j-waldby@pat7.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: linkBe 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).