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 16:52:18 +0000	[thread overview]
Message-ID: <bug-109891-4-qY58rFZ0ZU@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 #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Michel Morin from comment #3)
> From the safety point of view, I agree with you. But, at the same time, I
> thought that detectable UB (with the help of sanitizers) is useful than
> silent bug. 

Detectable UB doesn't guarantee detection. Sanitizers are not suitable for
production code. Introducing UB here would be strictly less safe, full stop.

And the bug isn't silent, it makes the stream unusable.

> How about `throw`ing as in std::string's constructor?

Set the exception flag on the stream and you get an exception when badbit is
set.

  parent reply	other threads:[~2023-05-17 16:52 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
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 [this message]
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-qY58rFZ0ZU@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).