public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: marduk@mandatory.net To: gcc-gnats@gcc.gnu.org Subject: preprocessor/6844: Seg fault when trying to preprocess a file with lots of #define's Date: Tue, 28 May 2002 05:36:00 -0000 [thread overview] Message-ID: <20020528122558.19120.qmail@sources.redhat.com> (raw) >Number: 6844 >Category: preprocessor >Synopsis: Seg fault when trying to preprocess a file with lots of #define's >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue May 28 05:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: marduk@mandatory.net >Release: gcc 3.1 >Organization: >Environment: Linux Redhat 7.2 ( 2.4.9-32 ) kernel gcc compiled with orginal 7.2 gcc. >Description: We are trying to preprocess a file with lots of #define's. At the end of the file the C preprocessor stumbles. lot of : invalid preprocessing directive #define then gcc: Internal error: Segmentation fault (program cpp0) >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-28 12:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-28 5:36 marduk [this message] 2002-05-28 7:18 neil 2002-05-29 23:22 neil
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=20020528122558.19120.qmail@sources.redhat.com \ --to=marduk@mandatory.net \ --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).