public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de To: Andreas.Krakowczyk@fujitsu-siemens.com, Erwin.Unruh@fujitsu-siemens.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gdr@gcc.gnu.org Subject: Re: c++/2455: [2003-01-01]Segfault in cc1plus on mutually inclusive namespaces Date: Mon, 24 Feb 2003 21:23:00 -0000 [thread overview] Message-ID: <20030224212358.19470.qmail@sources.redhat.com> (raw) Synopsis: [2003-01-01]Segfault in cc1plus on mutually inclusive namespaces State-Changed-From-To: analyzed->closed State-Changed-By: cae State-Changed-When: Mon Feb 24 21:23:58 2003 State-Changed-Why: Duplicate of 9798 but 9798 has been marked as a high prio regression. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2455
next reply other threads:[~2003-02-24 21:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-24 21:23 ehrhardt [this message] 2003-03-11 15:56 Volker Reichelt
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=20030224212358.19470.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=Andreas.Krakowczyk@fujitsu-siemens.com \ --cc=Erwin.Unruh@fujitsu-siemens.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gdr@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).