forked from OSchip/llvm-project
89385633ba
This issue was detected by ASan in one of our tests. This test manually invokes basic_filebuf::cloe(). fclose(__h.release() returned a non-zero exit status, so __file_ wasn't set to 0. Later when basic_filebuf destructor ran, we would enter the if (__file_) block again leading to heap-use-after-free error. The POSIX specification for fclose says that independently of the return value, fclose closes the underlying file descriptor and any further access (including another call to fclose()) to the stream results in undefined behavior. This is exactly what happened in our test case. To avoid this issue, we have to always set __file_ to 0 independently of the fclose return value. Differential Revision: https://reviews.llvm.org/D64979 llvm-svn: 366730 |
||
|---|---|---|
| .. | ||
| algorithms | ||
| atomics | ||
| containers | ||
| depr | ||
| diagnostics | ||
| experimental | ||
| input.output | ||
| iterators | ||
| language.support | ||
| localization | ||
| numerics | ||
| re | ||
| strings | ||
| thread | ||
| utilities | ||
| nothing_to_do.pass.cpp | ||