From c007cf5db9bda048d78480f60e809313a95b26c9 Mon Sep 17 00:00:00 2001 From: Philippe Waroquiers Date: Thu, 13 Sep 2018 21:12:56 +0200 Subject: [PATCH] Mention --keep-debuginfo=yes in the FAQ for unloaded shared objects. --- docs/xml/FAQ.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml index 47adf6b20d..d0d917edce 100644 --- a/docs/xml/FAQ.xml +++ b/docs/xml/FAQ.xml @@ -293,10 +293,12 @@ collect2: ld returned 1 exit status symbol tables (programs should be unstripped unless you run 'strip' on them; some libraries ship stripped). - Also, for leak reports involving shared objects, if the shared - object is unloaded before the program terminates, Valgrind will - discard the debug information and the error message will be full of - ??? entries. The workaround here is to avoid + Also, for leak reports involving shared objects, if the shared object + is unloaded before the program terminates, Valgrind will discard the debug + information and the error message will be full of ??? + entries. If you use the option , then + Valgrind will keep the debug information in order to show the stack traces, + at the price of increased memory. An alternate workaround is to avoid calling dlclose on these shared objects. Also, and -- 2.47.2