public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gccbz.10.petechap at spamgourmet dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53984] New: iostream operation throwing exception when exceptions not enabled
Date: Mon, 16 Jul 2012 16:11:00 -0000	[thread overview]
Message-ID: <bug-53984-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53984

             Bug #: 53984
           Summary: iostream operation throwing exception when exceptions
                    not enabled
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gccbz.10.petechap@spamgourmet.com


I'm getting an exception thrown in a situation where I believe a failbit should
be set instead.
Is my expectation wrong?

-------------------
#include <fstream>
#include <sstream>

int main()
{
    std::ifstream in(".");
    std::ostringstream out;
    if (in)
      in >> out.rdbuf();
}
-------------------


terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_filebuf::underflow error reading the file
Aborted (core dumped)


             reply	other threads:[~2012-07-16 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 16:11 gccbz.10.petechap at spamgourmet dot com [this message]
2012-07-16 17:00 ` [Bug libstdc++/53984] " gccbz.10.petechap at spamgourmet dot com
2012-07-16 17:26 ` redi at gcc dot gnu.org
2013-12-04 16:05 ` tom at kera dot name
2014-05-20 22:45 ` igorlord at alum dot mit.edu

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