LeakSanitizer:获取运行时泄漏报告?

时间:2015-10-18 18:00:00

标签: c++ linux multithreading memory-leaks address-sanitizer

我继承了一些遗留代码,似乎某处有内存泄漏。我的第一直觉就是用

编译
-faddress=sanitize -fno-omit-frame-pointer

让Address Sanitizer的工具系列为我找到漏洞。然而,我非常失望。我希望有一些运行时错误信息(类似于地址清理程序的错误,当你读或写你不应该写的内存)。在程序成功完成之前,泄漏消毒剂似乎没有进行任何泄漏检查分析。我的问题是我继承的代码有几个主题,并没有设计加入所有代码以准备软着陆。

我在一个简单的例子中简化了我的问题:

#include <thread>                                           
#include <chrono>                                           
#include <iostream>                                         

bool exit_thread = false;                                   

void threadFunc()                                           
{                                                           
   while(!exit_thread)                                      
   {                                                        
      char* leak = new char[256];                           
      std::this_thread::sleep_for(std::chrono::seconds{1}); 
   }                                                        
}                                                           

int main() {                                                
   std::thread t(threadFunc);                               
   std::cout << "Waiting\n";                                
   std::this_thread::sleep_for(std::chrono::seconds{5});    
   exit_thread = true;                                      
   std::cout << "Exiting\n";                                
   //Without joining here I do not get the leak report.     
   t.join();                                                
   return 0;                                                
}    

我用

编译它
clang++ leaker.cpp -fsanitize=address -fno-omit-frame-pointer -g -O0 -std=c++1y -o leaker      

然后用

运行
ASAN_OPTIONS='detect_leaks=1' LSAN_OPTIONS='exitcode=55:report_objects=true:log_threads=true:log_pointers=true' ./leaker                                                

(我对#34; LSAN_OPTIONS&#34有点疯狂;因为我正在玩这个......没有一个选项可以做我想要的但是在学习泄漏时退出了。)

如代码中所述,如果我加入线程然后退出程序,我会得到一个非常好的泄漏报告。否则我一无所获。因为您可以在遗留代码库中对10-100个线程进行映像跟踪,使得它们都能很好地运行,这是不实用的。

几年前,我记得和Visual Leak Detector一起玩,并且运气好,因为它会生成所有潜在内存泄漏的报告(而且我不记得必须把所有东西都弄得很好) 。问题是此工具仅适用于Windows,我的代码仅适用于Linux。我可以让LeakSanitizer工具做类似的事情吗?

1 个答案:

答案 0 :(得分:5)

LeakSanitizer(sanitizer/lsan_interface.h)的公共界面具有各种可满足您需求的功能。函数__lsan_do_leak_check()执行检查并在发现泄漏时终止。还有__lsan_do_recoverable_leak_check,它不会终止,可以多次调用。

考虑对您的计划进行此修改:

#include <thread>
#include <chrono>
#include <iostream>
#include <sanitizer/lsan_interface.h>

bool exit_thread = false;

void threadFunc()
{
   while(!exit_thread)
   {
      char* leak = new char[256];
      std::this_thread::sleep_for(std::chrono::seconds{1});
   }
}

int main() {
   std::thread t(threadFunc);
   std::cout << "Waiting\n";
   std::this_thread::sleep_for(std::chrono::seconds{5});
   exit_thread = true;
   std::cout << "Exiting\n";
   //Without joining here I do not get the leak report.
   //t.join();
   __lsan_do_recoverable_leak_check();
   std::cout << "Done\n";
   return 0;
}

输出:

Waiting
Exiting

=================================================================
==29240==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 1024 byte(s) in 4 object(s) allocated from:
    #0 0x4d9a30 in operator new[](unsigned long) (leaker+0x4d9a30)
    #1 0x4dc663 in threadFunc() leaker.cpp:12:20
    #2 0x4dffe3 in void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) /usr/bin/../lib64/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../../include/c++/5.2.0/functional:1530:18
    #3 0x4dff94 in std::_Bind_simple<void (*())()>::operator()() /usr/bin/../lib64/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../../include/c++/5.2.0/functional:1520:16
    #4 0x4dfcc8 in std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() /usr/bin/../lib64/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../../include/c++/5.2.0/thread:115:13
    #5 0x7f0a9664034f in execute_native_thread_routine /build/gcc-multilib/src/gcc-5.2.0/libstdc++-v3/src/c++11/thread.cc:84

SUMMARY: AddressSanitizer: 1024 byte(s) leaked in 4 allocation(s).
Done
terminate called without an active exception
Aborted