我正在努力解决一个神秘的问题,我只在我的RHEL4发布版本中看到了这个问题。我的一些单元测试(使用Boost1.36单元测试框架)在RHEL4 (gcc 3.4.6)和使用发布构建类型上失败。我没有看到使用RHEL5发布或调试构建类型(gcc 4.1.2,boost-1.39)的问题;我也没有看到使用Visual Studio2005(使用boost-1.36)或2008 (使用boost-1.39)的Windows32位或64位的问题。
怀疑这可能是由于一些微妙的内存问题,我继续在测试应用程序上运行valgrind (保留问题的最小情况)。下面是我在"full,no-reachable“模式下运行valgrind得到的结果:
==12285== Memcheck, a memory error detector.
==12285== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==12285== Using LibVEX rev 1575, a library for dynamic binary translation.
==12285== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP.
==12285== Using valgrind-3.1.1, a dynamic binary instrumentation framework.
==12285== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al.
==12285== For more details, rerun with: -v
==12285==
==12285== My PID = 12285, parent PID = 12284. Prog and args are:
==12285== ./myprojd
==12285==
==12285== Syscall param sigaltstack(ss) points to uninitialised byte(s)
==12285== at 0x3AD682EDA9: sigaltstack (in /lib64/tls/libc-2.3.4.so)
==12285== by 0x6488638: boost::detail::signal_handler::~signal_handler()
(in /<path_to>/libboost_unit_test_framework-gcc34-mt-1_36.so.1.36.0)
==12285== by 0x648975E: boost::execution_monitor::catch_signals
(boost::unit_test::callback0<int> const&)
(in /<path_to>/libboost_unit_test_framework-gcc34-mt-1_36.so.1.36.0)
==12285== by 0x6489813: boost::execution_monitor::execute
(boost::unit_test::callback0<int> const&)
(in /<path_to>/libboost_unit_test_framework-gcc34-mt-1_36.so.1.36.0)
==12285== by 0x648F2E4: boost::unit_test::framework::run(unsigned long, bool)
(in /<path_to>/libboost_unit_test_framework-gcc34-mt-1_36.so.1.36.0)
==12285== by 0x649BD02: boost::unit_test::unit_test_main(bool (*)(), int, char**)
(in /<path_to>/libboost_unit_test_framework-gcc34-mt-1_36.so.1.36.0)
==12285== by 0x4147F0: main (init.cpp:132)
==12285== Address 0x7FEFFF3B0 is on thread 1's stack
==12285==
==12285== ERROR SUMMARY: 6 errors from 1 contexts (suppressed: 4 from 1)
==12285== malloc/free: in use at exit: 190,112 bytes in 1,869 blocks.
==12285== malloc/free: 23,128 allocs, 21,259 frees, 2,520,845 bytes allocated.
==12285== For counts of detected errors, rerun with: -v
==12285== searching for pointers to 1,869 not-freed blocks.
==12285== checked 2,184,272 bytes.
==12285==
==12285== LEAK SUMMARY:
==12285== definitely lost: 0 bytes in 0 blocks.
==12285== possibly lost: 0 bytes in 0 blocks.
==12285== still reachable: 190,112 bytes in 1,869 blocks.
==12285== suppressed: 0 bytes in 0 blocks.
==12285== Reachable blocks (those to which a pointer was found) are not shown.
==12285== To see them, rerun with: --show-reachable=yes当然,我是在调试模式下运行的(尽管如我所提到的,该错误只在发布模式下发生)。如果我在发布模式下运行valgrind,我会得到相同的输出(可能只有更少的细节,比如line #s)。由此看来,问题出在boost-1.36中,或者可能是我对init_unit_test_suite的定义?显然,我可以尝试在所有平台上使用boost-1.39运行;但不幸的是,我们目前使用的是RHEL4和VS2005的boost-1.36,所以这可能还不实用。
我还观察到,在测试失败时,将某个记录器输出强制到控制台,可以使测试通过(我知道这不是很好)!我怀疑这可能是因为我注释了所有记录器输出并运行valgrind -这就是上面发布的内容。如果您需要init_unit_test_suite函数的一些代码片段;如果它有帮助,我可以发布它。任何解决这个问题的想法都是受欢迎的,我们非常感谢。
2011/05/26编辑:
这是init_unit_test_suite -如果有人能看一下,我将不胜感激。
std::ofstream log_stream;
std::ofstream report_stream;
const_string retrieve_framework_parameter( const_string cla_name, int argc, char** argv ) {
//- first try to find parameter among command line arguments if present
if( argc ) {
//- locate corresponding cla name
if( !cla_name.is_empty() ) {
for( int i = 1; i < argc; ++i ) {
if( cla_name == const_string( argv[i], cla_name.size() ) && argv[i][cla_name.size()] == '=' ) {
const_string result = argv[i] + cla_name.size() + 1;
for( int j = i; j < argc; ++j ) {
argv[j] = argv[j+1];
}
--argc;
return result;
}
}
}
}
return std::getenv( cla_name.begin() );
}
//! Format results to CPP UNIT xml
class simple_report_formatter : public results_reporter::format {
public:
virtual void results_report_start( std::ostream&) {
}
virtual void results_report_finish( std::ostream&) {
}
virtual void test_unit_report_start(test_unit const&, std::ostream&) {
}
virtual void test_unit_report_finish(test_unit const& tu, std::ostream& out) {
if( tu.p_type == tut_case ) {
const test_results& r = results_collector.results(tu.p_id);
if( r.passed() ) {
out<<"[PASS] ";
} else {
out<<"[FAIL] ";
}
out<<"Test Case <unit_"<<tu.p_name.get()<<"> ";
if( !r.passed() ) {
out<<" - ";
out<<"!! Assertions failed: "<<r.p_assertions_failed;
out<<" - See log files for details on failures !!";
}
out<<std::endl;
#if defined(MYPROJ_WINDOWS) && defined(MYPROJ_DEBUG)
if( !r.passed() ) {
std::ostringstream msg;
msg<<"!! "<<tu.p_name.get()<<" FAILED !!"<<std::endl;
OutputDebugStringA(msg.str().c_str());
}
#endif
}
}
virtual void do_confirmation_report(test_unit const&, std::ostream&) {
}
};
bool init_unit_test_suite() {
const_string log_file = retrieve_framework_parameter(
"--log_file",
framework::master_test_suite().argc,
framework::master_test_suite().argv
);
if( !log_file.empty() ) {
log_stream.open(log_file.begin());
unit_test_log.set_stream(log_stream);
}
const_string report_file = retrieve_framework_parameter(
"--report_file",
framework::master_test_suite().argc,
framework::master_test_suite().argv
);
if( !report_file.empty() ) {
report_stream.open(report_file.begin());
results_reporter::set_stream(report_stream);
}
if( runtime_config::report_format() == CLF ) {
results_reporter::set_format(new simple_report_formatter);
}
// This is providing the sensible default configuration when the test is being run
// without any input parameters whatsoever: print the final report to console
if( framework::master_test_suite().argc <= 1 ) {
results_reporter::set_stream(std::cout);
results_reporter::set_format(new simple_report_formatter);
results_reporter::set_level(DETAILED_REPORT);
}
framework::master_test_suite().p_name.set(MYPROJ_TEST_SUITE_NAME);
return true;
}发布于 2011-06-18 18:08:42
valgrind中的这个“错误”不一定是问题。在Linux中调用系统调用时,内存通常必须从用户空间复制到内核空间。在这样做时,它可能会复制未初始化的字节。
仅仅因为它将这些字节复制到内核空间并不意味着内核实际上会对未初始化的字节做任何事情。内核如何处理字节在很大程度上取决于所讨论的系统调用的语义。
Valgrind没有简单的方法来知道系统调用中传递的一些字节是否未初始化,因此它总是发出错误信号。许多类似的错误都被valgrind抑制了。
您可以在以下文件中看到valgrind的一些默认抑制:/usr/lib/valgrind/default.supp如果愿意,还可以创建自己的抑制文件,并在单元测试中使用它们来抑制错误消息。如果您在此系统上没有遇到任何实际问题,那么抑制错误可能是一个好主意。请参见valgrind的命令行选项。
https://stackoverflow.com/questions/6101531
复制相似问题