public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, rdhunt@sandia.gov
Subject: Re: libstdc++/7111: cout of null pointer causes core dump
Date: Wed, 03 Jul 2002 10:02:00 -0000	[thread overview]
Message-ID: <20020703170245.28230.qmail@sources.redhat.com> (raw)

Synopsis: cout of null pointer causes core dump

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Wed Jul  3 10:02:45 2002
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Wed Jul  3 10:02:45 2002
State-Changed-Why:
    Cannot reproduce with gcc-3_1-branch or mainline gcc. It's been fixed in both with:
    
    2002-05-24  Benjamin Kosnik  <bkoz@redhat.com>
    
    	PR libstdc++/6750
    	* include/bits/ostream.tcc (ostream::operator<<(const char*)): Fix
    	for empty string literal.
    	(ostream::operator<<(const _CharT*)): Same.
    	(ostream<char>::operator<<(const char*)): Same.
    	(ostream<char>::operator<<(streambuf*)): Same.
    	* testsuite/27_io/ostream_inserter_char.cc (test08): Add tests.
    	* testsuite/27_io/ostream_inserter_other.cc (test02): Modify.
    
    
    -benjamin

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


             reply	other threads:[~2002-07-03 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-03 10:02 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-04 10:01 bkoz
2002-07-03 10:46 Phil Edwards
2002-06-24 15:35 rdhunt

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=20020703170245.28230.qmail@sources.redhat.com \
    --to=bkoz@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=rdhunt@sandia.gov \
    /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).