public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pme@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rd.mora@econz.co.nz
Subject: Re: c++/4043: g++ seg fault with user basic_ostream constructor
Date: Fri, 28 Dec 2001 15:04:00 -0000	[thread overview]
Message-ID: <20011228230451.26843.qmail@sources.redhat.com> (raw)

Synopsis: g++ seg fault with user basic_ostream constructor

State-Changed-From-To: open->analyzed
State-Changed-By: pme
State-Changed-When: Fri Dec 28 15:04:51 2001
State-Changed-Why:
    Changing categories:  it's an ICE, not a library problem.  It
    is fixed with 3.1, as Craig mentioned, but continues to happen
    with 3.0.3.

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


             reply	other threads:[~2001-12-28 23:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 15:04 pme [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01 14:57 bangerth
2001-08-16 17:16 rd.mora

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=20011228230451.26843.qmail@sources.redhat.com \
    --to=pme@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rd.mora@econz.co.nz \
    /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).