我正在玩一些variant
和any classes
,我试着找出是否有更快的替代boost::spirit::hold_any
,或者它是否是最快的解决方案。有没有比这更快的东西?
也许是一个子问题,记忆博士说any_hold
导致memory leaks
,这是真的吗? (我听到了一些有关这方面的事情,但我想也许这是固定的或只是谣言,我使用的是Boost 1.57.0)
在这种情况下,记忆博士的可靠性如何?
我执行的代码主要是:
int main()
{
boost::spirit::hold_any a;
for (unsigned int i = 0; 150000 > i; ++i)
{
a = 5;
a = 5.0;
}
return 0;
}
记忆博士的日志文件:
Dr. Memory version 1.8.1 build 0 built on Feb 17 2015 19:08:31
Dr. Memory results for pid 6208: "boostTest.exe"
Application cmdline: ""C:\Users\tim.junge\Documents\Visual Studio 2010\Projects\C++\Backup\boostTest\Debug\boostTest.exe""
Recorded 108 suppression(s) from default C:\Users\tim.junge\Documents\Visual Studio 2010\Projects\C++\DrMemory-Windows-1.8.1-RC1\bin\suppress-default.txt
Error #1: LEAK 8 direct bytes 0x00a801d8-0x00a801e0 + 0 indirect bytes
# 0 replace_operator_new [d:\drmemory_package\common\alloc_replace.c:2613]
# 1 boost::spirit::basic_hold_any<>::assign<> [c:\boost_1_57_0\boost\spirit\home\support\detail\hold_any.hpp:293]
# 2 boost::spirit::basic_hold_any<>::operator=<> [c:\boost_1_57_0\boost\spirit\home\support\detail\hold_any.hpp:305]
# 3 main [c:\users\tim.junge\documents\visual studio 2010\projects\c++\backup\boosttest\boosttest\main.cpp:50]
Error #2: LEAK 8 direct bytes 0x00a87810-0x00a87818 + 0 indirect bytes
# 0 replace_operator_new [d:\drmemory_package\common\alloc_replace.c:2613]
# 1 boost::spirit::basic_hold_any<>::assign<> [c:\boost_1_57_0\boost\spirit\home\support\detail\hold_any.hpp:293]
# 2 boost::spirit::basic_hold_any<>::operator=<> [c:\boost_1_57_0\boost\spirit\home\support\detail\hold_any.hpp:305]
# 3 main [c:\users\tim.junge\documents\visual studio 2010\projects\c++\backup\boosttest\boosttest\main.cpp:212]
Reached maximum leak report limit (-report_leak_max). No further leaks will be reported.
===========================================================================
FINAL SUMMARY:
DUPLICATE ERROR COUNTS:
Error # 2: 9992
SUPPRESSIONS USED:
ERRORS FOUND:
0 unique, 0 total unaddressable access(es)
0 unique, 0 total uninitialized access(es)
0 unique, 0 total invalid heap argument(s)
0 unique, 0 total GDI usage error(s)
0 unique, 0 total handle leak(s)
0 unique, 0 total warning(s)
2 unique, 9993 total, 79944 byte(s) of leak(s)
0 unique, 0 total, 0 byte(s) of possible leak(s)
ERRORS IGNORED:
1 potential leak(s) (suspected false positives)
(details: C:\Users\tim.junge\Documents\Visual Studio 2010\Projects\C++\DrMemory-Windows-1.8.1-RC1\drmemory\logs\DrMemory-boostTest.exe.6208.000\potential_errors.txt)
0 unique, 0 total, 0 byte(s) of still-reachable allocation(s)
(re-run with "-show_reachable" for details)
50204 leak(s) beyond -report_leak_max
Details: C:\Users\tim.junge\Documents\Visual Studio 2010\Projects\C++\DrMemory-Windows-1.8.1-RC1\drmemory\logs\DrMemory-boostTest.exe.6208.000\results.txt
答案 0 :(得分:0)
我刚刚在2小时前了解了hold_any,但我会尽我所能:)
简答:
我经历了一些测试,了解到,当你设置时:
a = 5;
您实际上是将POINTER(“object”)值设置为0x000005。没有清理和内存泄漏(?)
LONG ANSWER +其他信息: 这会以某种方式导致内存泄漏
但是,在设置变量类型时,一切似乎都很好:
boost::spirit::hold_any a;
for (unsigned int i = 0; 15000000 > i; ++i)
{
//a = 5; //no cleanup on scope loss
a = size_t(5); //seems fine
a = float(5.0); //seems fine
}
我在其他地方读到一个空的hold_any(没有初始数据类型)导致内存泄漏(那个人提交了一个补丁boost::spirit::hold_any memory corruption,不确定它是否已经实现)。这似乎是你的情况。
所以,在分配新数据时,确保它有一个类型,或者在初始化它时设置类型(?)我会建议安全:
boost::spirit::hold_any a(size_t(15));
for (unsigned int i = 0; 15000000 > i; ++i)
{
a = 5; //no memory leak, but invalid for classes - like std::string
}
另外,获取/修改数据的替代方法(因为我没有看到太多文档):
size_t* c = boost::spirit::any_cast<size_t>(&a); //pointer will be 0 if its not a size_t
size_t &c2 = *(boost::spirit::any_cast<size_t>(&a)); //runtime error if not a size_t
size_t &c3 = boost::spirit::any_cast<size_t&>(a); //runtime error if not a size_t
用于检查数据类型
if (int * i = boost::spirit::any_cast<int>(&a)) // an int?
//if (int& i = boost::spirit::any_cast<int&>(a)) // runtime error
const bool anInt = true;
if (size_t* i = boost::spirit::any_cast<size_t>(&a)) // a size_t?
const bool aSizeT = true;