我有一个可以使用boost::anyboost::spirit::hold_any的大型代码库(取决于宏定义)。
hold_any似乎与boost::any(例如How to print boost::any to a stream?Type erasure - Part IV)兼容并且速度更快(Why you shouldn’t use boost::any),但是我使用hold_any(Boost v1.55 / 1.54 / 1.53)遇到了一些分段错误错误。

这是一个最小的工作示例,与原始代码存在相同的问题:

#include <iostream>
#include <string>
#include <vector>

#include <boost/spirit/home/support/detail/hold_any.hpp>

typedef boost::spirit::hold_any any;
typedef std::vector<any> vany;

int main()
{
  vany data0, data1;

  for (unsigned i(0); i < 1000; ++i)
  {
    std::string s("test_test_test");
    data0.push_back(any(s));
  }

  const unsigned n(data0.size());
  vany::iterator iter(data0.begin());

  for (unsigned i(0); i < n; ++i)
  {
    std::cout << "Moving " << i << std::endl;

    data1.push_back(*iter);
    iter = data0.erase(iter);
  }

  return 0;
}

该程序似乎正常工作:
  • boost::spirit::hold_any变为boost::any;
  • hold_any的内容更改为足够小的数据类型以执行小的缓冲区优化(例如,从std::stringint)。

  • 在广泛使用的库(例如Boost Spirit)中可能存在一些重大错误,这似乎很奇怪,但是
  • 我很难在示例中发现错误;
  • 我尝试g++ / clang++失败。

  • 这个例子怎么了?

    最佳答案

    出于某种原因,您应该而不是使用hold_any,因为它在detail/hold_any.hpp中是存在的。

    就是说,hold_any的副本分配似乎已损坏。我已经使用建议的修复程序创建了 a pull request on github

    如果没有修复,以下程序将演示UB(因为编译器会生成首选的浅层赋值运算符):

    #include <iostream>
    #include <string>
    
    #include <boost/spirit/home/support/detail/hold_any.hpp>
    
    typedef boost::spirit::hold_any any;
    
    int main()
    {
        any b;
        {
            any a;
            a = std::string("test_test_test");
            b = a;
        }
    
        std::cout << "b: " << b << '\n';
    }
    

    在valgrind下运行时:
    ==11827== Invalid read of size 8
    ==11827==    at 0x5E9D793: std::basic_ostream<char, std::char_traits<char> >& std::operator<< <char, std::char_traits<char>, std::allocator<char> >(std::basic_ostream<char, std::char_traits<char> >&, std::basic_string<char, std
    ==11827==    by 0x4012FC: boost::spirit::detail::fxns<mpl_::bool_<true> >::type<std::string, char>::stream_out(std::ostream&, void* const*) (hold_any.hpp:113)
    ==11827==    by 0x4010F5: std::basic_ostream<char, std::char_traits<char> >& boost::spirit::operator<< <char>(std::basic_ostream<char, std::char_traits<char> >&, boost::spirit::basic_hold_any<char> const&) (hold_any.hpp:368)
    ==11827==    by 0x400FC9: main (test.cpp:17)
    ==11827==  Address 0x8ac1650 is 0 bytes inside a block of size 39 free'd
    ==11827==    at 0x4C2BADC: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
    ==11827==    by 0x5EC405E: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.18)
    ==11827==    by 0x401204: boost::spirit::detail::fxns<mpl_::bool_<true> >::type<std::string, char>::static_delete(void**) (hold_any.hpp:89)
    ==11827==    by 0x401328: boost::spirit::basic_hold_any<char>::~basic_hold_any() (hold_any.hpp:246)
    ==11827==    by 0x4010B4: boost::spirit::basic_hold_any<char>::~basic_hold_any() (hold_any.hpp:245)
    ==11827==    by 0x400FA0: main (test.cpp:15)
    

    关于c++ - boost::spirit::hold_any内存损坏,我们在Stack Overflow上找到一个类似的问题:https://stackoverflow.com/questions/24065769/

    10-11 22:38
    查看更多