使用valgrind在mysql c ++客户端中查找内存泄漏

我正在使用valgrind来尝试跟踪内存泄漏是从MySQL分发的mysql c ++客户端。

在这两个例子（resultset.cpp）和我自己的程序中，都有一个56字节的块没有被释放。 在我自己的程序中，我已经追踪到泄漏到一个调用mysql客户端。

运行testing时，结果如下：

valgrind --leak-check=full --show-reachable=yes ./my-executable ==29858== Memcheck, a memory error detector ==29858== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==29858== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==29858== Command: ./my-executable ==29858== ==29858== ==29858== HEAP SUMMARY: ==29858== in use at exit: 56 bytes in 1 blocks ==29858== total heap usage: 693 allocs, 692 frees, 308,667 bytes allocated ==29858== ==29858== 56 bytes in 1 blocks are still reachable in loss record 1 of 1 ==29858== at 0x4C284A8: malloc (vg_replace_malloc.c:236) ==29858== by 0x400D334: _dl_map_object_deps (dl-deps.c:506) ==29858== by 0x4013652: dl_open_worker (dl-open.c:291) ==29858== by 0x400E9C5: _dl_catch_error (dl-error.c:178) ==29858== by 0x4012FF9: _dl_open (dl-open.c:583) ==29858== by 0x7077BCF: do_dlopen (dl-libc.c:86) ==29858== by 0x400E9C5: _dl_catch_error (dl-error.c:178) ==29858== by 0x7077D26: __libc_dlopen_mode (dl-libc.c:47) ==29858== by 0x72E5FEB: pthread_cancel_init (unwind-forcedunwind.c:53) ==29858== by 0x72E614B: _Unwind_ForcedUnwind (unwind-forcedunwind.c:126) ==29858== by 0x72E408F: __pthread_unwind (unwind.c:130) ==29858== by 0x72DDEB4: pthread_exit (pthreadP.h:265) ==29858== ==29858== LEAK SUMMARY: ==29858== definitely lost: 0 bytes in 0 blocks ==29858== indirectly lost: 0 bytes in 0 blocks ==29858== possibly lost: 0 bytes in 0 blocks ==29858== still reachable: 56 bytes in 1 blocks ==29858== suppressed: 0 bytes in 0 blocks ==29858== ==29858== For counts of detected and suppressed errors, rerun with: -v ==29858== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 6) 

我有几个关于这个问题的问题：

• 这个valgrind错误是什么意思？
• 私密脏内存可能是泄露内存的指示吗？
• 内存仍然可以修复的错误，但为什么？
• 什么是肮脏的私人记忆？
• Upstart init正在泄漏内存，你怎么debugging它？

1. 我应该怎样解释–show-reachable块？
2. 那个块对我来说是有用的吗？
3. 如果该块没有用，valgrind是否有另一种机制可以帮助我追踪泄漏？
4. 如果没有，有没有其他的工具（希望Linux上的OSS）来帮助我缩小这个范围？

提前致谢..

更新：这是我在我的系统上为pthread_exit的定义find的代码。 我不确定这是被调用的实际源。 但是，如果是的话，谁能解释一下可能会出现什么问题？

 void pthread_exit (void *retval) { /* specific to PTHREAD_TO_WINTHREAD */ ExitThread ((DWORD) ((size_t) retval)); /* thread becomes signalled so its death can be waited upon */ /*NOTREACHED*/ assert (0); return; /* void fnc; can't return an error code */ }