这是一个bug，clang v3.4用libc ++ 没有展现这种行为; GCC 4.8的libstdc ++ 仍然。

从libstdc ++源和异常的文本，我会说 basic_ios :: clear 不捕获从调用堆栈中抛出的异常，并应用是异常标志在播放？ 。

去年已经提出错误53984 。

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)).

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.