在 Visual Studio 2019 下为 Debug 模型编译时，哪些配置错误可能会导致 Boost Filesystem 因访问冲突而失败？

Question

我很难理解为什么我使用 boost 的一些代码在 Visual Studio 2017 下运行良好，但现在在 Visual Studio 2019 下导致访问冲突。但是，我只遇到调试构建下的此失败。发布版本运行良好，没有任何问题。

我在我的构建、环境或代码中有什么设置不正确，可能会导致这样的失败？

我的环境：

Windows 10
提升 1.74（动态 link）
Visual Studio 2019 v16.7.6
为 C++ x64 编译

我的代码失败的行是这样的：

boost::filesystem::path dir = (boost::filesystem::temp_directory_path() / boost::filesystem::unique_path("%%%%-%%%%-%%%%-%%%%"));

Boost 文件系统中的失败行是 boost/filesystem/path.hpp 中的此处：

namespace path_traits
{  //  without codecvt

  inline
    void convert(const char* from,
    const char* from_end,    // 0 for null terminated MBCS
    std::wstring & to)
  {
    convert(from, from_end, to, path::codecvt());
  }

Visual Studio报错信息如下：

Exception thrown at 0x00007FF9164F1399 (vcruntime140d.dll) in ezv8.tests.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

调用堆栈如下所示：

    vcruntime140d.dll!00007ff9164f1550()    Unknown
>   boost_filesystem-vc142-mt-gd-x64-1_74.dll!wmemmove(wchar_t * _S1, const wchar_t * _S2, unsigned __int64 _N) Line 248    C++
    boost_filesystem-vc142-mt-gd-x64-1_74.dll!std::_WChar_traits<wchar_t>::move(wchar_t * const _First1, const wchar_t * const _First2, const unsigned __int64 _Count) Line 204 C++
    boost_filesystem-vc142-mt-gd-x64-1_74.dll!std::wstring::append(const wchar_t * const _Ptr, const unsigned __int64 _Count) Line 2864 C++
    boost_filesystem-vc142-mt-gd-x64-1_74.dll!std::wstring::append<wchar_t *,0>(wchar_t * const _First, wchar_t * const _Last) Line 2916    C++
    boost_filesystem-vc142-mt-gd-x64-1_74.dll!`anonymous namespace'::convert_aux(const char * from, const char * from_end, wchar_t * to, wchar_t * to_end, std::wstring & target, const std::codecvt<wchar_t,char,_Mbstatet> & cvt) Line 77 C++
    boost_filesystem-vc142-mt-gd-x64-1_74.dll!boost::filesystem::path_traits::convert(const char * from, const char * from_end, std::wstring & to, const std::codecvt<wchar_t,char,_Mbstatet> & cvt) Line 153   C++
    appsvcs.dll!boost::filesystem::path_traits::convert(const char * from, const char * from_end, std::wstring & to) Line 1006  C++
    appsvcs.dll!boost::filesystem::path_traits::dispatch<std::wstring>(const std::string & c, std::wstring & to) Line 257   C++
    appsvcs.dll!boost::filesystem::path::path<char [20]>(const char[20] & source, void * __formal) Line 168 C++

我在整个代码中使用 UTF-8 字符串，因此我已将 boost::filesystem 配置为期望 UTF-8 字符串，如下所示：

boost::nowide::nowide_filesystem();

Answer 1

这个问题的原因原来是 _ITERATOR_DEBUG_LEVEL. This setting does affect ABI compatibility. I was setting this flag (to 0) in my own code, but it was not set in the Boost build. The solution is to either remove the flag from one's own code, or add the flag to the Boost build by adding define=_ITERATOR_DEBUG_LEVEL=0 to the b2 arguments (from another stack overflow answer) 的不一致使用。

在 Visual Studio 2019 下为 Debug 模型编译时，哪些配置错误可能会导致 Boost Filesystem 因访问冲突而失败？

What misconfiguration might cause Boost Filesystem to fail with an access violation when compiled for Debug model under Visual Studio 2019?

boost-locale