public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109891] Null pointer special handling in ostream's operator << for C-strings
Date: Wed, 17 May 2023 14:32:25 +0000	[thread overview]
Message-ID: <bug-109891-4-kVPSttTPGF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109891-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109891

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
--- a/libstdc++-v3/include/bits/ostream.tcc
+++ b/libstdc++-v3/include/bits/ostream.tcc
@@ -306,6 +306,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
     basic_ostream<_CharT, _Traits>&
     operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s)
     {
+      _GLIBCXX_DEBUG_PEDANTIC(__s != 0);
       if (!__s)
        __out.setstate(ios_base::badbit);
       else

  parent reply	other threads:[~2023-05-17 14:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 14:20 [Bug libstdc++/109891] New: " mimomorin at gmail dot com
2023-05-17 14:28 ` [Bug libstdc++/109891] " redi at gcc dot gnu.org
2023-05-17 14:32 ` redi at gcc dot gnu.org [this message]
2023-05-17 15:10 ` mimomorin at gmail dot com
2023-05-17 15:13 ` pinskia at gcc dot gnu.org
2023-05-17 16:52 ` redi at gcc dot gnu.org
2023-05-18 15:08 ` mimomorin at gmail dot com
2023-05-18 15:36 ` redi at gcc dot gnu.org
2023-05-18 16:01 ` xry111 at gcc dot gnu.org
2023-05-20 12:58 ` mimomorin at gmail dot com
2023-07-09 21:33 ` pinskia at gcc dot gnu.org

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=bug-109891-4-kVPSttTPGF@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).