c++ 内存泄漏、死锁之valgrind定位问题

已于 2023-02-22 22:21:11 修改
阅读量1.1k 收藏 4
点赞数 1
分类专栏： 服务器性能分析与疑难问题定位 文章标签： c++ linux 运维
于 2022-10-08 21:22:21 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/weixin_44834554/article/details/127212901
版权
本文介绍了Linux下开源的内存泄漏检测工具valgrind，包括其核心组件、常用的memcheck和Helgrind工具的使用，以及如何通过valgrind检测内存泄漏和多线程程序中的竞争问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

c++系列文章目录

文章目录

前言

该篇主要介绍开源的内存泄漏工具 valgrind，valgrind 是一套 Linux 下，开放源代码的动态调试工具集合，能够检测内存管理错误、线程 BUG 等，valgrind 由内核（core）以及基于内核的其他调试工具组成。内核类似于一个框（framework），它模拟了一个 CPU 环境，并提供服务给其他工具；而其他工具则类似于插件 (plug-in)，利用内核提供的服务完成各种特定的内存调试任务。

一、valgrind 是什么？

Valgrind是一套Linux下，开放源代码（GPL V2）的仿真调试工具的集合。Valgrind由内核（core）以及基于内核的其他调试工具组成。内核类似于一个框架（framework），它模拟了一个CPU环境，并提供服务给其他工具；而其他工具则类似于插件 (plug-in)，利用内核提供的服务完成各种特定的内存调试任务。

valgrind包括的工具如下：
memcheck，这是valgrind应用最广泛的工具，一个重量级的内存检查器，能够发现开发中绝大多数内存错误使用情况，比如：使用未初始化的内存，使用已经释放了的内存，内存访问越界等。
callgrind，主要用来检查程序中函数调用过程中出现的问题。
cachegrind，主要用来检查程序中缓存使用出现的问题。
helgrind，主要用来检查多线程程序中出现的竞争问题。
massif，主要用来检查程序中堆栈使用中出现的问题。
extension，可以利用core提供的功能，自己编写特定的内存调试工具。

valgrind有很多功能，本文仅仅介绍了一种最基本的应用。

二、valgrind环境搭建

1.环境安装

wget https://sourceware.org/pub/valgrind/valgrind-3.2.1.tar.bz2 --no-check-certificate
解压
tar -jxvf valgrind-3.14.0.tar.bz2 
安装目录
cd valgrind-3.14.0
./configure --prefix=/home/user1/valgrind
make
make install
//设置环境变量
vim ~/.bashrc
export PATH=$PATH:~/valgrind/bin/
source ~/.bashrc

或者安装通过
yum install valgrind

如下方式来观察内存泄漏
valgrind --tool=memcheck --leak-check=full --error-limit=no --num-callers=50 --show-reachable=yes --log-file=./valgrind_report.log ./mytest

--tool=memcheck : 使用内存检测的工具
--leak-check=full : 有设置这个选项时，当被测程序结束时查找内存泄露。设置为summary，Valgrind会统计有多少内存泄露发生，若设置为full、yes，Valgrind会给出每一个独立的泄露的详细信息
--error-limit=no:如果错误太多要停止显示新的错误的选项
--num-callers=50:这个值默认是12，最高是50。表示显示多少层的堆栈，设置越高会使Valgrind运行越慢而且使用更多的内存,但是在嵌套调用层次比较高的程序中非常实用
--log-file=/home/davit/valgrind_report.log： 指定检测结果报告的存放路径和文件名
./xxxx： 执行被测可执行文件
--show-reachable=yes

三、valgribd的memcheck 使用步骤

1.Memcheck
最常用的工具，用来检测程序中出现的内存问题，所有对内存的读写都会被检测到，一切对malloc()/free()/new/delete的调用都会被捕获。所以，它能检测以下问题：

1.对未初始化内存的使用；
2.读/写释放后的内存块；
3.读/写超出malloc分配的内存块；
4.读/写不适当的栈中内存块；
5.内存泄漏，指向一块内存的指针永远丢失；
6.不正确的malloc/free或new/delete匹配；
7.memcpy()相关函数中的dst和src指针重叠。

#include <iostream> 
#include <unistd.h> 
#include <string.h> 
#include <iostream>
#include <fstream>
int fun(char* pData,int size)
{
    const char *recordpath = "/opt/eDisk/davit.test"; 
    std::ofstream outfile;
    outfile.open(recordpath, std::ios_base::out|std::ios_base::app);
    outfile.write((const char*) pData, size);
    return 0;
}

int memLeakage()
{
    char *pMemory = new char [1024];
    memset(pMemory,1,1024); 
    fun(pMemory,1024);
}
int main(int argc, char* argv[]) 
{
    memLeakage();
    sleep(60);
    return 0;
}

编译：
g++ test.cpp -o mytest -std=c++11 -g -fno-elide-constructors
内存泄漏检测：
valgrind --tool=memcheck --leak-check=full --error-limit=no --num-callers=50 --show-reachable=yes --log-file=./valgrind_report.log ./mytest

==29711== Memcheck, a memory error detector
==29711== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==29711== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==29711== Command: ./mytest
==29711== Parent PID: 17468
==29711== 
==29711== 
==29711== Process terminating with default action of signal 2 (SIGINT)
==29711==    at 0x571C9E0: __nanosleep_nocancel (in /usr/lib64/libc-2.17.so)
==29711==    by 0x571C893: sleep (in /usr/lib64/libc-2.17.so)
==29711==    by 0x40124B: main (test.cpp:339)
==29711== 
==29711== HEAP SUMMARY:
==29711==     in use at exit: 1,024 bytes in 1 blocks
==29711==   total heap usage: 3 allocs, 2 frees, 9,784 bytes allocated
==29711== 
==29711== 1,024 bytes in 1 blocks are definitely lost in loss record 1 of 1
==29711==    at 0x4C2AC38: operator new[](unsigned long) (vg_replace_malloc.c:433)
==29711==    by 0x401200: memLeakage() (test.cpp:331)
==29711==    by 0x401241: main (test.cpp:338)
==29711== 
==29711== LEAK SUMMARY:
==29711==    definitely lost: 1,024 bytes in 1 blocks
==29711==    indirectly lost: 0 bytes in 0 blocks
==29711==      possibly lost: 0 bytes in 0 blocks
==29711==    still reachable: 0 bytes in 0 blocks
==29711==         suppressed: 0 bytes in 0 blocks
==29711== 
==29711== For lists of detected and suppressed errors, rerun with: -s
==29711== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

通过检测报告，本代码种存在一个内存泄漏的问题，即函数memLeakge存在内存泄漏，这样就很容易判断问题了。
在这里插入图片描述

四、valgrind的Helgrind使用步骤

Helgrind
它主要用来检查多线程程序中出现的竞争问题。Helgrind寻找内存中被多个线程访问，而又没有一贯加锁的区域，
这些区域往往是线程之间失去同步的地方，而且会导致难以发掘的错误。Helgrind实现了名为“Eraser”的竞争检测算法，并做了进一步改进，减少了报告错误的次数。不过，Helgrind仍然处于实验阶段。

#include <thread>
#include <mutex>
#include <stdio.h>
#include <unistd.h> 
#include <iostream>
#include <memory>
#include <string.h>

std::mutex _ma;
std::mutex _mb;

void threadAB()
{
    std::cout<< "in threadAB" <<std::endl;
    std::unique_lock<std::mutex> locka(_ma);
    std::this_thread::sleep_for(std::chrono::milliseconds(100));
    std::unique_lock<std::mutex> lockb(_mb);
    std::cout<< "out threadAB2" <<std::endl;
}

void threadBA()
{
    std::cout<< "in threadBA" <<std::endl;
    std::unique_lock<std::mutex> lockb(_mb);
    //std::this_thread::sleep_for(std::chrono::milliseconds(1));
    std::unique_lock<std::mutex> locka(_ma);
    std::cout<< "out threadBA2" <<std::endl;
}
void test2()
{
    auto t1 = std::thread(threadAB);
    auto t2 = std::thread(threadBA);
    t1.join();
    t2.join();          
}

int main()
{
    test2();
    std::cout<< "helloworld" <<std::endl;
    return 0;
}

编译：
g++ -g test.cpp -lpthread -std=c++11 -o MyLesson
内存泄漏检测：
valgrind --tool=helgrind --log-file=./valgrind_report.log ./test

==9131== Helgrind, a thread error detector
==9131== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
==9131== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==9131== Command: ./test
==9131== Parent PID: 9074
==9131== 
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- Ignoring non-Dwarf2/3/4 block in .debug_info
--9131-- WARNING: Serious error when reading debug info
--9131-- When reading debug info from /usr/lib64/libstdc++.so.6.0.30:
--9131-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
==9131== ---Thread-Announcement------------------------------------------
==9131== 
==9131== Thread #3 was created
==9131==    at 0x5A8492E: clone (in /usr/lib64/libc-2.17.so)
==9131==    by 0x4E43059: do_clone.constprop.4 (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4E44569: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4C30CEA: pthread_create_WRK (hg_intercepts.c:427)
==9131==    by 0x4C31DC8: pthread_create@* (hg_intercepts.c:460)
==9131==    by 0x512AC2E: std::thread::_M_start_thread(std::shared_ptr<std::thread::_Impl_base>, void (*)()) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x512ACFF: std::thread::_M_start_thread(std::shared_ptr<std::thread::_Impl_base>) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4019A1: std::thread::thread<void (&)()>(void (&)()) (thread:135)
==9131==    by 0x4012C9: test2() (test.cpp:32)
==9131==    by 0x401336: main (test.cpp:39)
==9131== 
==9131== ---Thread-Announcement------------------------------------------
==9131== 
==9131== Thread #2 was created
==9131==    at 0x5A8492E: clone (in /usr/lib64/libc-2.17.so)
==9131==    by 0x4E43059: do_clone.constprop.4 (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4E44569: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4C30CEA: pthread_create_WRK (hg_intercepts.c:427)
==9131==    by 0x4C31DC8: pthread_create@* (hg_intercepts.c:460)
==9131==    by 0x512AC2E: std::thread::_M_start_thread(std::shared_ptr<std::thread::_Impl_base>, void (*)()) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x512ACFF: std::thread::_M_start_thread(std::shared_ptr<std::thread::_Impl_base>) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4019A1: std::thread::thread<void (&)()>(void (&)()) (thread:135)
==9131==    by 0x4012B8: test2() (test.cpp:31)
==9131==    by 0x401336: main (test.cpp:39)
==9131== 
==9131== ----------------------------------------------------------------
==9131== 
==9131== Possible data race during read of size 8 at 0x605118 by thread #3
==9131== Locks held: none
==9131==    at 0x518426E: std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x51846D6: std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x401207: threadBA() (test.cpp:23)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==    by 0x4E43EA4: start_thread (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x5A8496C: clone (in /usr/lib64/libc-2.17.so)
==9131== 
==9131== This conflicts with a previous write of size 8 by thread #2
==9131== Locks held: none
==9131==    at 0x5184330: std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x51846D6: std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x401132: threadAB() (test.cpp:14)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==  Address 0x605118 is 24 bytes inside data symbol "_ZSt4cout@@GLIBCXX_3.4"
==9131== 
==9131== ----------------------------------------------------------------
==9131== 
==9131== Possible data race during write of size 8 at 0x605118 by thread #3
==9131== Locks held: none
==9131==    at 0x5184330: std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x51846D6: std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x401207: threadBA() (test.cpp:23)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==    by 0x4E43EA4: start_thread (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x5A8496C: clone (in /usr/lib64/libc-2.17.so)
==9131== 
==9131== This conflicts with a previous write of size 8 by thread #2
==9131== Locks held: none
==9131==    at 0x5184330: std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x51846D6: std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x401132: threadAB() (test.cpp:14)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==  Address 0x605118 is 24 bytes inside data symbol "_ZSt4cout@@GLIBCXX_3.4"
==9131== 
==9131== ----------------------------------------------------------------
==9131== 
==9131== Possible data race during read of size 1 at 0x546C898 by thread #3
==9131== Locks held: none
==9131==    at 0x518406A: std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x401214: threadBA() (test.cpp:23)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==    by 0x4E43EA4: start_thread (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x5A8496C: clone (in /usr/lib64/libc-2.17.so)
==9131== 
==9131== This conflicts with a previous write of size 1 by thread #2
==9131== Locks held: none
==9131==    at 0x5125BFC: std::ctype<char>::_M_widen_init() const (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x5184097: std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x40113F: threadAB() (test.cpp:14)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==  Address 0x546c898 is 56 bytes inside data symbol "_ZN12_GLOBAL__N_17ctype_cE"
==9131== 
==9131== ----------------------------------------------------------------
==9131== 
==9131== Possible data race during read of size 1 at 0x546C8A3 by thread #3
==9131== Locks held: none
==9131==    at 0x5184073: std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x401214: threadBA() (test.cpp:23)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==    by 0x4E43EA4: start_thread (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x5A8496C: clone (in /usr/lib64/libc-2.17.so)
==9131== 
==9131== This conflicts with a previous write of size 8 by thread #2
==9131== Locks held: none
==9131==    at 0x5125B21: std::ctype<char>::_M_widen_init() const (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x5184097: std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&) (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x40113F: threadAB() (test.cpp:14)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131==    by 0x402933: std::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() (thread:115)
==9131==    by 0x512AB07: execute_native_thread_routine_compat (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4C30EDE: mythread_wrapper (hg_intercepts.c:389)
==9131==  Address 0x546c8a3 is 67 bytes inside data symbol "_ZN12_GLOBAL__N_17ctype_cE"
==9131== 
==9131== 
==9131== Process terminating with default action of signal 2 (SIGINT)
==9131==    at 0x4E45017: pthread_join (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4C2DF81: pthread_join_WRK (hg_intercepts.c:553)
==9131==    by 0x4C31DD3: pthread_join (hg_intercepts.c:572)
==9131==    by 0x512A9F2: std::thread::join() (in /usr/lib64/libstdc++.so.6.0.30)
==9131==    by 0x4012D5: test2() (test.cpp:33)
==9131==    by 0x401336: main (test.cpp:39)
==9131== ----------------------------------------------------------------
==9131== 
==9131== Thread #3: Exiting thread still holds 1 lock
==9131==    at 0x4E4A54D: __lll_lock_wait (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4E45E9A: _L_lock_883 (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4E45D66: pthread_mutex_lock (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4C2E2EB: mutex_lock_WRK (hg_intercepts.c:902)
==9131==    by 0x4C321AD: pthread_mutex_lock (hg_intercepts.c:925)
==9131==    by 0x40105B: __gthread_mutex_lock(pthread_mutex_t*) (gthr-default.h:748)
==9131==    by 0x4015BF: std::mutex::lock() (mutex:134)
==9131==    by 0x401AAA: std::unique_lock<std::mutex>::lock() (mutex:511)
==9131==    by 0x401666: std::unique_lock<std::mutex>::unique_lock(std::mutex&) (mutex:443)
==9131==    by 0x401236: threadBA() (test.cpp:26)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131== 
==9131== ----------------------------------------------------------------
==9131== 
==9131== Thread #2: Exiting thread still holds 1 lock
==9131==    at 0x4E4A54D: __lll_lock_wait (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4E45E9A: _L_lock_883 (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4E45D66: pthread_mutex_lock (in /usr/lib64/libpthread-2.17.so)
==9131==    by 0x4C2E2EB: mutex_lock_WRK (hg_intercepts.c:902)
==9131==    by 0x4C321AD: pthread_mutex_lock (hg_intercepts.c:925)
==9131==    by 0x40105B: __gthread_mutex_lock(pthread_mutex_t*) (gthr-default.h:748)
==9131==    by 0x4015BF: std::mutex::lock() (mutex:134)
==9131==    by 0x401AAA: std::unique_lock<std::mutex>::lock() (mutex:511)
==9131==    by 0x401666: std::unique_lock<std::mutex>::unique_lock(std::mutex&) (mutex:443)
==9131==    by 0x401187: threadAB() (test.cpp:17)
==9131==    by 0x402A40: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (functional:1732)
==9131==    by 0x40299A: std::_Bind_simple<void (*())()>::operator()() (functional:1720)
==9131== 
==9131== 
==9131== Use --history-level=approx or =none to gain increased speed, at
==9131== the cost of reduced accuracy of conflicting-access information
==9131== For lists of detected and suppressed errors, rerun with: -s
==9131== ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 34 from 24)

在这里插入图片描述

–

总结

本文就是抛砖引玉，希望你能够更好的使用valgrind，它能够帮你解决很多问题。

valgrind 分析死锁
陌上花开缓缓归以的博客
11-05 201
【1】里面的1 表示owner，从上面的打印可以看到mutex 2和 3和owner形成了相互等待的过程，所以造成了死锁。运行后死锁后ctrl+c发送退出信号退出进程。2，代码pthread.c。
【C++内存泄漏】使用历史版本比对法排查C++程序中的内存泄漏问题
dvlinker的技术专栏
08-07 1万+
本文详细讲述如何使用历史版本比对法去排查C++程序中的内存泄漏问题，并对内存泄漏的相关细节点进行了展开。
Linux C/C++ 内存泄漏检测工具：Valgrind
aizong2453的博客
12-07 235
　　Valgrind 是一款 Linux下（支持 x86、x86_64和ppc32）程序的内存调试工具，它可以对编译后的二进制程序进行内存使用监测（C语言中的malloc和free，以及C++中的new和delete），找出内存泄漏问题。　　Valgrind 中包含的 Memcheck 工具可以检查以下的程序错误：　　使用未初始化的内存 (Use of uninitialised mem...
Linux C++编程死锁排查
计算机毕业论文源码，学生个人网页制作html源码。贴近用户做网络推广和互联网优化。
03-13 1063
在 Linux 环境下进行 C++ 编程时，多线程能显著提升程序的并发处理能力，让程序在面对复杂任务时表现得更加高效。但多线程编程并非一帆风顺，死锁问题就像隐藏在暗处的 “杀手”，随时可能让程序陷入僵局。想象一下，你的程序原本运行得好好的，突然就像被施了定身咒一样，毫无反应，所有的线程都被卡住，无法继续推进。这很可能就是死...
linux多线程互斥锁程序卡死排查 /valgrind
asitMJ的博客
01-03 1003
发现程序退出了有锁没有被释放 #通过thread 6找到了是324行创建的线程函数里面锁的释放有问题。我借助工具是valgrind，能够用来检查内存泄漏、死锁和其他线程问题。gcc编译程序用 -g 选项来编译程序，以便在可执行文件中包含调试信息。可以看到程序运行时候每个函数堆栈分配了多少个，还存在多少个。这个是每个线程运行完了之后，有多少个锁还没有释放。运行程序发现程序卡住。
死锁问题分析的利器——valgrind的DRD和Helgrind
方亮的专栏
08-02 5631
在《DllMain中不当操作导致死锁问题的分析--死锁介绍》一文中，我们介绍了死锁产生的原因。一般来说，如果我们对线程同步技术掌握不牢，或者同步方案混乱，极容易导致死锁。本文我们将介绍如何使用valgrind排查死锁问题。（转载请指明出于breaksoftware的csdn博客） 构造一个场景 #include &lt;pthread.h&gt; pthre...
内存泄漏、死锁怎么检测？
a13602955218的博客
09-19 229
内存泄漏：valgrind，gpreftools，vs自带的内存检测工具 死锁： 详见：https://blog.youkuaiyun.com/a13602955218/article/details/108685059 调试：gdb调试线上代码，打印堆栈信息
【内存泄漏】＜valgrind＞
luoye_369的博客
09-29 313
运行时必须指明想用的工具，如果省略工具名，默认运行memcheck。
【C++内存泄漏】使用历史版本比对法排查C++程序中的内存泄漏问题（同时总结了引发内存泄漏的常见场景）
热门推荐
dvlinker的技术专栏
12-27 2万+
本文详细讲述如何使用历史版本比对法去排查C++程序中的内存泄漏问题，并对内存泄漏的相关细节点进行了展开。
C++如何追踪内存泄漏（valgrind/ASan等）并定位到业务代码
最新发布
大模型大数据攻城狮的专栏
05-03 264
在C++开发中，内存泄漏是一个难以避免却又必须解决的问题。由于C++赋予了开发者对内存的直接控制权，任何疏忽都可能导致资源未被正确释放，进而引发性能下降甚至程序崩溃。随着项目规模的扩大，手动排查内存泄漏变得异常困难，借助专业的检测工具成为了开发者的必然选择。这些工具能够帮助我们快速定位内存泄漏的发生位置，甚至在某些情况下直接指向业务代码中的问题根源。
c++程序如何排查死锁
k1419197516的博客
08-06 482
这里会说出，哪儿哪儿他创建了线程，退出的时候，哪个线程拿住了lock，通过什么方式拿的，在第几行。当然你得用-g来编译，如果不是debug模式的话，也会有信息，只是不会指定说在cpp的几行，但能够知道在哪个函数内发生。用valgrind的helgrind工具。
进程、线程死锁和内存泄漏检测工具-Valgrind
荒野
11-28 353
死锁检测工具vargrind包含DRD和Helgrind检测工具。
c++ 死锁检测与内存泄露
xiaofeilongyu的博客
04-02 1774
通过hook函数从写malloc/free函数，每次malloc都回创建一个.mem文件，free会将申请内存时创建的文件删除，当mem文件夹下存在文件时，说明会有内存泄露，查看文件中内存可以查询到具体在哪里发生内存泄露。valgrind是一款内存错误检测工具，而helgrind是valgrind工具集成的一款工具，用于检测多线程程序中的竞争条件和死锁；helgrind通过获取模拟死锁的获取和释放来检测线程之间是否存在非法的资源访问序列，从而查找可能出现死锁的编程错误。超时后释放已经获取的资；
关于项目中的内存问题、死锁问题如何定位？——Valgrind
weixin_44322824的博客
09-12 389
用调试工具调试这个core 文件也能定位到代码行， 但是从对应行的代码看， 可能这行代码本身并没有什么问题， 它只是一个“被陷害者”。3、使用valgrind分析以后发现有一个类内成员变量出现了越界。一切对malloc()/free()/new/delete的调用都会被捕获。在实际处理器的基础上仿真一个虚拟处理器，使应用程序运行于这个虚拟处理器之上，从而进行监视分析。内存泄漏、越界可以用valgrind工具包的Memcheck工具进行定位。1、当时的core文件并没有提供相关的信息。
C++——linux下valgrind工具检测内存泄露和性能分析
Map的博客
03-26 1411
1. Valgrind简介 官网Valgrind介绍是一款用于内存调试、内存泄漏检测以及性能分析的软件开发工具。这些工具之中最有名的是Memcheck。它能够识别很多C或者C++程序中内存相关的错误，这些错误会导致程序崩溃或者出现不可预知的行为。 1)memcheck：检查程序中的内存问题，如泄漏、越界、非法指针等(本文重点学习)。 2)callgrind：检测程序代码的运行时间和调用过程，...
C++ 内存泄漏检测工具——Valgrind（Linux系统）
可爱满分的博客
03-14 2283
前六种是比较常见的问题，内存泄漏主要是有（4）（5）引起的，由于程序中申请了空间，但是没有在程序结束或是在函数结束时正确的释放，导致这段空间被无法在后面的程序中继续使用。对于数据量较大的程序，这是很危险的，由于内存占用问题，尽管函数或程序可能执行完毕，但是未被释放，但是内存仍被占用，这些空间无法后续使用或被其他程序使用，可能会导致计算机运行变慢，也可能导致后续程序无法正常运行。–log-file=< file > 将输出的信息写入到filename.PID的文件里，PID是运行程序的进行ID。
Linux C/C++下内存泄露检查神器Valgrind
chen1415886044的博客
08-17 1030
项目中由于各方面因素，总是有人抱怨存在内存泄漏，系统长时间运行之后，可用内存越来越少，甚至导致了某些服务起不来。实际上，使用C/C++这类没有垃圾回收机制的语言时，你很多时间都花在处理如何正确释放内存上。为以后更方便的检测内存泄漏问题，于是学习使用了valgrind来对内存泄漏进行检测。 Valgrind是linux环境下的一款功能齐全的内存调试和性能分析工具集，它包括Memcheck、Callgrind、Cachegrind、Helgrind、Massif等工具。本文旨在介绍Valgrind工具集中的内存
Linux c++ - Valgrind的安装与使用
莫忘输赢的博客
11-08 678
一、获取源码 wget http://www.valgrind.org/downloads/valgrind-3.14.0.tar.bz2 二、解压 tar -jxvf valgrind-3.14.0.tar.bz2 三、进入目录,进行安装,其中/home/user1/valgrind是你想安装的目录 cd valgrind-3.14.0 ./configure --prefix=/home/user1/valgrind make make install 四、配置环境变量 1、打开~
死锁编程定位分析
郝大侠的博客
08-08 337
1.死锁概念 死锁是指两个或者两个以上的进程在执行过程中，因抢夺资源而造成的一种互相等待的现象，若无外力干涉它们将都无法推进下去，如果系统资源充足，进程的资源请求都能够得到满足，死锁出现的可能性也就很低，否则就会因争夺有限的资源而陷入死锁。 2.死锁原因 系统资源不足 进程运行推进的顺序不合适 资源分配不当 class LockThread implements Runnable{ ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

c+猿辅导

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值