CODEWITHSUNDEEP
c++iostream
user2249683
user2249683

Reputation:

Unexpected exception in std::ifstream

Experimenting with I/O I get an exception where no exception should have been thrown:

#include <iostream>
#include <fstream>

int main()
{
    std::ifstream f("/tmp");
    std::cout << "Exception Flags: " << f.exceptions() << std::endl;
    if(f >> std::ws) std::cout << "This will not succeed" << std::endl;
    else std::cout << "Ok - it fails" << std::endl;
    return 0;
}

But the output is:

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

g++ (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2

Edit

The test is supposed to fail without exception:

From 27.5.5.4 basic_ios flags functions

void clear(iostate state = goodbit);

4 Postcondition: If rdbuf()!=0 then state == rdstate(); otherwise rdstate()==(state | ios_base::badbit).

5 Effects: If ((state | (rdbuf() ? goodbit : badbit)) & exceptions()) == 0, returns. Otherwise, the function throws an object fail of class basic_ios::failure (27.5.3.1.1), constructed with implementation-defined argument values.

void setstate(iostate state);

6 Effects: Calls clear(rdstate() | state) (which may throw basic_ios::failure (27.5.3.1.1)).

Upvotes: 6

Views: 2900

Answers (1)

Lightness Races in Orbit
Lightness Races in Orbit

Reputation: 385098

It's a bug, and clang v3.4 with libc++ doesn't exhibit this behaviour; GCC 4.8's libstdc++ still does.

From the libstdc++ source and the text of the exception, I'd say that basic_ios::clear is not catching exceptions thrown from down the call stack and applying the "are exception flags in play?" logic before potentially rethrowing them.

It was already raised last year as bug 53984.

Upvotes: 7

Related Questions