public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/6084: cpp Segmentation Fault Date: Fri, 29 Mar 2002 12:16:00 -0000 [thread overview] Message-ID: <20020329201601.18695.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/6084; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.demon.co.uk> To: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com> Cc: "'neil@gcc.gnu.org'" <neil@gcc.gnu.org>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, "'joshg@hf.intel.com'" <joshg@hf.intel.com>, "'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>, "'rnesius@ichips.intel.com'" <rnesius@ichips.intel.com>, "Nguyen, Tuan" <tuan.nguyen@intel.com>, "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org> Subject: Re: preprocessor/6084: cpp Segmentation Fault Date: Fri, 29 Mar 2002 20:06:38 +0000 Gerwin, Joshua A wrote:- > A minor experiment in option removal shows that the problem is potentially > tied to the > -dD tag. Compare: > [...] > > A clue, no? A clue, but not much more. Sadly I can't reproduce the issue on x86 Linux. Would you mind running it through gdb, and giving a backtrace of the line it segfaults on, and any relevant-looking variables? Thanks, Neil.
next reply other threads:[~2002-03-29 20:16 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-29 12:16 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-21 13:34 neil 2002-05-21 13:33 neil 2002-04-17 23:52 neil 2002-04-15 19:46 Gerwin, Joshua A 2002-04-15 18:06 Richard Henderson 2002-04-15 12:06 'Neil Booth' 2002-04-15 11:36 Gerwin, Joshua A 2002-04-15 11:16 'Neil Booth' 2002-04-15 11:06 Gerwin, Joshua A 2002-04-13 1:26 Phil Edwards 2002-04-13 1:16 Phil Edwards 2002-04-12 22:16 Neil Booth 2002-04-12 16:06 Gerwin, Joshua A 2002-04-12 13:36 Phil Edwards 2002-04-03 22:36 'Neil Booth' 2002-04-03 17:06 Gerwin, Joshua A 2002-04-02 22:36 Neil Booth 2002-03-29 11:36 Gerwin, Joshua A 2002-03-29 0:20 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=20020329201601.18695.qmail@sources.redhat.com \ --to=neil@daikokuya.demon.co.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).