Question

我从使用fedora rpm specfile从源代码构建的centos7，clang-3.6.1获得了完全相同的结果。 Ubuntu 14.04，clang-3.4

使用维基的说明https://github.com/google/sanitizers/wiki/MemorySanitizerLibcxxHowTo 尽可能接近。该页面最后更新6个月前。

谷歌版本613仍在使用tr1

In file included from /home/hal/googletest/src/gtest-all.cc:39:
In file included from /home/hal/googletest/include/gtest/gtest.h:58:
In file included from /home/hal/googletest/include/gtest/internal/gtest-internal.h:40:
/home/hal/googletest/include/gtest/internal/gtest-port.h:507:13: fatal error: 
      'tr1/tuple' file not found
#   include <tr1/tuple>  // NOLINT
            ^
1 error generated.

将googletest更新为提示（746），并使用以下警告进行编译

➜ [hal@davis 9:54 ~/gtest-msan] make
Scanning dependencies of target gtest
[ 50%] Building CXX object CMakeFiles/gtest.dir/src/gtest-all.cc.o
clang: warning: -lc++abi: 'linker' input unused
clang: warning: -lc++abi: 'linker' input unused
clang: warning: argument unused during compilation: '-L/home/hal/libcxx_msan/lib'
clang: warning: argument unused during compilation: '-L/home/hal/libcxx_msan/lib'
Linking CXX static library libgtest.a

来自该页面的琐碎建议案例并未被msan

接收

[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from FooTest
[ RUN      ] FooTest.Foo
test.cc:7: Failure
Value of: foo[4]
  Actual: '\0'
Expected: 'z'
Which is: 'z' (122, 0x7A)
[  FAILED  ] FooTest.Foo (1 ms)
[----------] 1 test from FooTest (1 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (1 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] FooTest.Foo

 1 FAILED TEST

我有一个valgrind barfs的项目，因为使用了一些非常大的mmaps，因此内存清理会非常有用。如果我做错了什么。似乎googletest以某种方式抑制了错误。删除谷歌测试并将测试用例转换为

if（foo [4] =='z'） std :: cout＆lt;＆lt; “它是z”＆lt;＆lt;的std :: ENDL;

按预期触发明显错误的报告

==29128== WARNING: MemorySanitizer: use-of-uninitialized-value
    #0 0x7f59270c1738 in std::string::_Rep::_M_is_leaked() const /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../include/c++/4.8.5/bits/basic_string.h:192:18
    #1 0x7f59270c1738 in std::string::_M_leak() /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../include/c++/4.8.5/bits/basic_string.h:316
    #2 0x7f59270c1738 in std::string::operator[](unsigned long) /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../include/c++/4.8.5/bits/basic_string.h:849
    #3 0x7f59270c1738 in main /home/hal/test-gtest-msan/test2.cc:7
    #4 0x7f5925c2bb14 in __libc_start_main (/lib64/libc.so.6+0x21b14)
    #5 0x7f592706ce30 in _start (/home/hal/test-gtest-msan/test2+0x35e30)

  Uninitialized value was created by an allocation of 'foo' in the stack frame of function 'main'
    #0 0x7f59270c12e0 in main /home/hal/test-gtest-msan/test2.cc:4

SUMMARY: MemorySanitizer: use-of-uninitialized-value /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../include/c++/4.8.5/bits/basic_string.h:192 std::string::_Rep::_M_is_leaked() const
Exiting

是否可以将内存清理与单元测试库一起使用？

Answer 1

它不是MemorySanitizer或googletest问题：显然libc ++最近发生了变化，现在它在实际的四字节字符串＆＃34; foo＆＃34;之外初始化字节，所以MSan没有生成报告这种越界访问。

MSan wiki已更新为使用其他示例，其错误报告为预期：

TEST(FooTest, Foo) {
  int uninitialized;
  EXPECT_GT(uninitialized, 5);
}

结果：

[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from FooTest
[ RUN      ] FooTest.Foo
==39032== WARNING: MemorySanitizer: use-of-uninitialized-value
    #0 0x48d73c in testing::AssertionResult testing::internal::CmpHelperGT<int, int>(char const*, char const*, int const&, int const&) googletest/include/gtest/gtest.h:1463:1
    #1 0x48ce7a in FooTest_Foo_Test::TestBody() test.cc:6:3
...

P.S。当您配置googletest以在版本613构建它时，可以添加-DGTEST_USE_OWN_TR1_TUPLE=1来编译标记。

Answer 2

由于单元测试中看到的值为'\0'，因此字符串实际上可以初始化位置4处的内存以与C字符串（尾随零）兼容。单元测试和手动测试用例之间的区别可能是编译器优化的结果。如果将字符串切换为std::vector<char>{'f', 'o', 'o'}会发生什么？

如果您也可以发布单元测试代码，将会很有帮助。

无法从项目的示例项目中重现内存清理结果

2 个答案: