|
From: Philippe W. <phi...@so...> - 2018-09-13 19:14:41
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=c007cf5db9bda048d78480f60e809313a95b26c9 commit c007cf5db9bda048d78480f60e809313a95b26c9 Author: Philippe Waroquiers <phi...@sk...> Date: Thu Sep 13 21:12:56 2018 +0200 Mention --keep-debuginfo=yes in the FAQ for unloaded shared objects. Diff: --- 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 47adf6b..d0d917e 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).</para> - <para>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 - <literal>???</literal> entries. The workaround here is to avoid + <para>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 <literal>???</literal> + entries. If you use the option <option>--keep-debuginfo=yes</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 <function>dlclose</function> on these shared objects.</para> <para>Also, <option>-fomit-frame-pointer</option> and |