From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23900 invoked by alias); 12 Feb 2003 21:32:59 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 23868 invoked by uid 48); 12 Feb 2003 21:32:58 -0000 Date: Wed, 12 Feb 2003 21:32:00 -0000 Message-ID: <20030212213258.23866.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sebor@roguewave.com From: paolo@gcc.gnu.org Reply-To: paolo@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sebor@roguewave.com, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/9555: ostream inserters fail to set badbit on exception X-SW-Source: 2003-02/txt/msg00540.txt.bz2 List-Id: Synopsis: ostream inserters fail to set badbit on exception State-Changed-From-To: open->analyzed State-Changed-By: paolo State-Changed-When: Wed Feb 12 21:32:58 2003 State-Changed-Why: Confirmed. This seems actually about the underlying implementation of xsputn in v3, which, not being equivalent to repeated calls to sputc, doesn't call overflow at all for this testcase! http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9555