public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/9555: ostream inserters fail to set badbit on exception
@ 2003-02-12 21:32 paolo
0 siblings, 0 replies; 4+ messages in thread
From: paolo @ 2003-02-12 21:32 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, sebor
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: libstdc++/9555: ostream inserters fail to set badbit on exception
@ 2003-04-18 3:51 bkoz
0 siblings, 0 replies; 4+ messages in thread
From: bkoz @ 2003-04-18 3:51 UTC (permalink / raw)
To: bkoz, gcc-bugs, gcc-prs, nobody, sebor
Synopsis: ostream inserters fail to set badbit on exception
Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Fri Apr 18 03:51:38 2003
Responsible-Changed-Why:
Mine.
State-Changed-From-To: analyzed->closed
State-Changed-By: bkoz
State-Changed-When: Fri Apr 18 03:51:38 2003
State-Changed-Why:
Fixed.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9555
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: libstdc++/9555: ostream inserters fail to set badbit on exception
@ 2003-02-22 21:56 Paolo Carlini
0 siblings, 0 replies; 4+ messages in thread
From: Paolo Carlini @ 2003-02-22 21:56 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR libstdc++/9555; it has been noted by GNATS.
From: Paolo Carlini <pcarlini@unitus.it>
To: gcc-gnats@gcc.gnu.org, sebor@roguewave.com, gcc-bugs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:
Subject: Re: libstdc++/9555: ostream inserters fail to set badbit on exception
Date: Sat, 22 Feb 2003 22:48:18 +0100
Correction, sorry.
Not relying too much on gdb, now I see that overflow _is_ in fact called.
Paolo.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9555
^ permalink raw reply [flat|nested] 4+ messages in thread
* libstdc++/9555: ostream inserters fail to set badbit on exception
@ 2003-02-03 20:26 sebor
0 siblings, 0 replies; 4+ messages in thread
From: sebor @ 2003-02-03 20:26 UTC (permalink / raw)
To: gcc-gnats
>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:
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-04-18 3:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-02-12 21:32 libstdc++/9555: ostream inserters fail to set badbit on exception paolo
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 3:51 bkoz
2003-02-22 21:56 Paolo Carlini
2003-02-03 20:26 sebor
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).