public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sebor@roguewave.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/9555: ostream inserters fail to set badbit on exception
Date: Mon, 03 Feb 2003 20:26:00 -0000	[thread overview]
Message-ID: <20030203201820.20736.qmail@sources.redhat.com> (raw)


>Number:         9555
>Category:       libstdc++
>Synopsis:       ostream inserters fail to set badbit on exception
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 03 20:26:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     sebor@roguewave.com
>Release:        3.2.1
>Organization:
>Environment:

>Description:
The expected exit status of the program below is 0. When compiled with gcc 3.2.1 and the supplied libstdc++, it is 1, indicating that the inserter fails to set badbit when an exception occurs during output.

Regards
Martin
>How-To-Repeat:
#include <ostream>
#include <streambuf>

struct buf: std::streambuf
{
    virtual int_type overflow (int_type) {
        throw 0;
        return -1;
    }
};

int main ()
{
    buf b;

    std::ostream strm (&b);

    strm.exceptions (std::ios::badbit);

    try {
        strm << 0;
    }
    catch (int) {
        return !(strm.bad ());
    }
    catch (...) {
        return 2;
    }

    return 3;
}
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-02-03 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 20:26 sebor [this message]
2003-02-12 21:32 paolo
2003-02-22 21:56 Paolo Carlini
2003-04-18  3:51 bkoz

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=20030203201820.20736.qmail@sources.redhat.com \
    --to=sebor@roguewave.com \
    --cc=gcc-gnats@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).