shared-libraries - 如何使用 Valgrind 跟踪动态加载的库？

Question

我有一个使用 dlopen 和 dlclose 加载/卸载库的进程。该库有一些内存泄漏，我想用 Valgrind 进行跟踪。我尝试了以下方法:

LD_PRELOAD=libmylibrary.so valgrind --leak-check=full myprogram

这是行不通的。我得到一个 undefined symbol 错误，因为库依赖于主程序中的一些符号。有没有其他方法可以使库在程序结束时保持加载状态？

Answer 1

这是一个老问题，但我相信如果他/她偶然发现了这个问题，这对将来的人会有帮助。

你可以传递--keep-debuginfo=yes参数给valgrind:

--keep-debuginfo=<yes|no> [default: no]

When enabled, keep ("archive") symbols and all other debuginfo for unloaded code. Thisallows saved stack traces to include file/line info for code that has been dlclose'd (orsimilar). Be careful with this, since it can lead to unbounded memory use for programs whichrepeatedly load and unload shared objects.

Some tools and some functionalities have only limited support for archived debug info.Memcheck fully supports it. Generally, tools that report errors can use archived debug info toshow the error stack traces. The known limitations are: Helgrind's past access stack trace of arace condition is does not use archived debug info. Massif (and more generally the xtree Massifoutput format) does not make use of archived debug info. Only Memcheck has been (somewhat) testedwith --keep-debuginfo=yes, so other tools may have unknown limitations.