public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, joshg@hf.intel.com, nobody@gcc.gnu.org, rnesius@ichips.intel.com, tuan.nguyen@intel.com Subject: Re: preprocessor/6084: cpp Segmentation Fault Date: Fri, 29 Mar 2002 00:20:00 -0000 [thread overview] Message-ID: <20020329082023.12179.qmail@sources.redhat.com> (raw) Synopsis: cpp Segmentation Fault State-Changed-From-To: open->feedback State-Changed-By: neil State-Changed-When: Fri Mar 29 00:20:22 2002 State-Changed-Why: Changed to category preprocessor; not a front end issue. Quite a surpise to me, too. I take pride in cpp not segfaulting 8-) Could you give me a testcase? I can't reproduce it with the information supplied. Or, could you try 3.0.4? There was a segfault fixed in the later 3.0 cycle, triggered by a combination of command line options, but I'm not sure which 3.0.x got it. Judging by your command line, I suspect it is caused by a certain combination of switches; can you reproduce it on a simple file like #include <stdio.h> or something? Alternatively, if you can't produce a simple testcase, but can get it to happen on Linux, then please send me the files so I can track this down, or tell me where it happens when you're debugging the cpp0 binary. Thanks! http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6084
next reply other threads:[~2002-03-29 8:20 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-29 0:20 neil [this message] 2002-03-29 11:36 Gerwin, Joshua A 2002-03-29 12:16 Neil Booth 2002-04-02 22:36 Neil Booth 2002-04-03 17:06 Gerwin, Joshua A 2002-04-03 22:36 'Neil Booth' 2002-04-12 13:36 Phil Edwards 2002-04-12 16:06 Gerwin, Joshua A 2002-04-12 22:16 Neil Booth 2002-04-13 1:16 Phil Edwards 2002-04-13 1:26 Phil Edwards 2002-04-15 11:06 Gerwin, Joshua A 2002-04-15 11:16 'Neil Booth' 2002-04-15 11:36 Gerwin, Joshua A 2002-04-15 12:06 'Neil Booth' 2002-04-15 18:06 Richard Henderson 2002-04-15 19:46 Gerwin, Joshua A 2002-04-17 23:52 neil 2002-05-21 13:33 neil 2002-05-21 13:34 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=20020329082023.12179.qmail@sources.redhat.com \ --to=neil@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=joshg@hf.intel.com \ --cc=nobody@gcc.gnu.org \ --cc=rnesius@ichips.intel.com \ --cc=tuan.nguyen@intel.com \ /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).