This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/69877] Problem with std::basic_ios::setstate()
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 19 Feb 2016 19:37:02 +0000
- Subject: [Bug libstdc++/69877] Problem with std::basic_ios::setstate()
- Auto-submitted: auto-generated
- References: <bug-69877-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69877
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Leo Carreon from comment #0)
> Please notice that the executable core dumped. Even if I try to catch the
> exception, it still core dumps. If I remember correctly, this did not
> happen on Fedora 22 which included g++ 5.1.1.
No, an unhandled exception results in abort() which always dumped core. That
hasn't changed.
The reason you can't catch it is that the library throws std::ios::failure but
you try to catch std::__cxx11::ios::failure, due to the default ABI changing in
F23. If you compile with -D_GLIBCXX_USE_CXX11_ABI=0 then you'll be able to
refer to the old exception type, but that changes the ABI.
The fact the old ABI exception is thrown is PR66145.
*** This bug has been marked as a duplicate of bug 66145 ***