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++/28103] std::operator<<(ostream&, string) sets badbit instead of failbit on failure
Date: Thu, 13 Jun 2024 16:45:47 +0000	[thread overview]
Message-ID: <bug-28103-4-4DxzaQNGJb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28103-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It looks like we've been setting badbit in ostream::_M_write(const charT*,
streamsize) since it was added in r0-47606-g8d0a564bba54f7

That function was used to replace the similar code in basic_ostream::write:

          streamsize __put = this->rdbuf()->sputn(__s, __n);
          if ( __put != __n)
            this->setstate(ios_base::badbit);

and in the operator<< for std::basic_string:

          streamsize __res = __out.rdbuf()->sputn(__s, __len);
          __out.width(0);
          if (__res != __len)
            __out.setstate(ios_base::failbit);

However that created the problem, because basic_ostream::write is indeed
specified to set badbit but the string inserter sets failbit.

[ostream.unformatted] says:
"inserting in the output sequence fails (in which case the function calls
setstate(badbit)"

[string.io] defers to [string.view.io] which defers to [ostream.formatted]
which says:
"If the generation fails, then the formatted output function does
setstate(ios_base::failbit)"

So we have different requirements for ostream::write and string insertion, but
we implement them both the same way since r0-47606-g8d0a564bba54f7 (the
_M_write member was later replaced  by __ostream_write but that uses the same
logic and sets badbit).

  parent reply	other threads:[~2024-06-13 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28103-4@http.gcc.gnu.org/bugzilla/>
2024-06-13 16:09 ` redi at gcc dot gnu.org
2024-06-13 16:13 ` redi at gcc dot gnu.org
2024-06-13 16:13 ` redi at gcc dot gnu.org
2024-06-13 16:45 ` redi at gcc dot gnu.org [this message]
2024-06-13 17:17 ` redi at gcc dot gnu.org
2024-06-14 11:15 ` redi at gcc dot gnu.org
2006-06-20 18:21 [Bug libstdc++/28103] New: " sebor at roguewave dot com
2006-06-20 19:09 ` [Bug libstdc++/28103] " pcarlini at suse dot de
2006-06-22 16:28 ` pcarlini at suse dot de

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-28103-4-4DxzaQNGJb@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).