ReadAnchor throws exception on second run about bitcoin HOT 6 CLOSED

Compile from source MinGW64, run twice..

What are the exact steps to reproduce, including the exact operating system version?

Does it happen with the compiled release version as well?

Ref: https://en.cppreference.com/w/cpp/filesystem/remove

from bitcoin.

Windows 10. I run the official binary on Linux and that's fine. Different compilers seem to manage the exception slightly differently? Regardless I'm not sure that a blind delete is the right way to do this, is all. Fixed on my side, I just wanted to point it out.

from bitcoin.

Different compilers seem to manage the exception slightly differently?

That should not be the case. The point of standard C++ library std::filesystem::remove is to provide the same interface behavior, regardless of compiler or operating system.

The specification says that false should be returned when the file does not exist, not an exception be thrown.

However, without exact steps to reproduce, using your compiler version, there is little that can be done here.

Regardless I'm not sure that a blind delete is the right way to do this, is all.

Right, it could make sense to catch the exception for other reasons, or not allow it to be thrown, but that is a different question.

from bitcoin.

According to #29930 (comment) the reason could be that you are using an experimental C++17 standard library, which has bugs?

from bitcoin.

That should not be the case. The point of standard C++ library std::filesystem::remove is to provide the same interface behavior, regardless of compiler or operating system.

The specification says that false should be returned when the file does not exist, not an exception be thrown.

Ah good point ><. I'll try it once with my clang install, it's a fair bit newer than my gcc which is due to be updated anyway. Ok to close from my side. Thanks.

from bitcoin.

Closing for now, but please leave a comment if there are more details to debug this issue.

from bitcoin.