8

我在 Mac OS 10.8.2 中使用 valgrind 3.8.1 我使用 Homebrew 安装了 Valgrind。

但是当我尝试在我的代码上运行 valgrind 时，我从库中得到了一大堆错误，这些错误我什至没有在我的代码中使用过。

valgrind --leak-check=full ./a.out

==92079== 
==92079== HEAP SUMMARY:
==92079==     in use at exit: 70,861 bytes in 362 blocks
==92079==   total heap usage: 529 allocs, 167 frees, 75,151 bytes allocated
==92079== 
==92079== 16 bytes in 1 blocks are definitely lost in loss record 7 of 85
==92079==    at 0x54D7: malloc_zone_malloc (in /usr/local/Cellar/valgrind/3.8.1/lib/valgrind/vgpreload_memcheck-amd64-darwin.so)
==92079==    by 0x373381: recursive_mutex_init (in /usr/lib/libobjc.A.dylib)
==92079==    by 0x372025: _objc_init (in /usr/lib/libobjc.A.dylib)
==92079==    by 0xBB27: libSystem_initializer (in /usr/lib/libSystem.B.dylib)
==92079==    by 0x7FFF5FC13377: ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC13761: ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC1006D: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC0FFC3: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC0FEB9: ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC01F9D: dyld::initializeMainExecutable() (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC05B03: dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) (in /usr/lib/dyld)
==92079==    by 0x7FFF5FC01396: dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) (in /usr/lib/dyld)
.....
..... 
.....
.....
==92079== 
==92079== LEAK SUMMARY:
==92079==    definitely lost: 16,816 bytes in 16 blocks
==92079==    indirectly lost: 1,168 bytes in 5 blocks
==92079==      possibly lost: 4,941 bytes in 67 blocks
==92079==    still reachable: 47,936 bytes in 274 blocks
==92079==         suppressed: 0 bytes in 0 blocks
==92079== Reachable blocks (those to which a pointer was found) are not shown.
==92079== To see them, rerun with: --leak-check=full --show-reachable=yes
==92079== 
==92079== For counts of detected and suppressed errors, rerun with: -v
==92079== ERROR SUMMARY: 21 errors from 21 contexts (suppressed: 0 from 0)

谁能展示如何抑制 Mac OS 10.8 的这些错误？（或者只显示我的代码的错误）

4

2 回答 2

2

抱歉，这不是您想听到的，但是如果您运行，valgrind ./a.out 您应该会看到类似于以下内容的输出

==18604== WARNING: Support on MacOS 10.8 is experimental and mostly broken.
==18604== WARNING: Expect incorrect results, assertions and crashes.
==18604== WARNING: In particular, Memcheck on 32-bit programs will fail to
==18604== WARNING: detect any errors associated with heap-allocated data.

即使你压制了你想要压制的东西，Valgrind 也很可能不会帮助你调试你的程序。如果您愿意使用 Xcode 自带的称为 Instruments 的内存分析工具。

于 2013-03-30T05:11:18.623 回答
2

valgrind v3.9.0解决了这个问题。尽管官方发布说明v3.9.0指出支持Mac OSX 10.8已得到改进。但它似乎也可以正常工作Mac OSX 10.9。

您可以在 Homebrew 上获取最新版本：

brew update
brew install valgrind
于 2014-02-21T18:22:58.437 回答