public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, larsbj@gullik.net,
	nobody@gcc.gnu.org
Subject: Re: c++/10454: [3.3?/3.4 regression] Segmentation fault when using std::stack
Date: Thu, 24 Apr 2003 00:27:00 -0000	[thread overview]
Message-ID: <20030424002739.8413.qmail@sources.redhat.com> (raw)

Old Synopsis: ICE: Segmentation fault when using std::stack
New Synopsis: [3.3?/3.4 regression] Segmentation fault when using std::stack

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Thu Apr 24 00:27:38 2003
State-Changed-Why:
    This is a duplicate of 10471, both by reducing your snippet
    as well as from looking at a backtrace. I had added some
    more information to 10471, so I close this one even though
    it is older. Thanks anyway!
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10454


                 reply	other threads:[~2003-04-24  0:27 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=20030424002739.8413.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=larsbj@gullik.net \
    --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: link
Be 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).