From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Thu, 13 Sep 2018 19:12:56 +0000 (+0200)
Subject: Mention --keep-debuginfo=yes in the FAQ for unloaded shared objects.
X-Git-Tag: VALGRIND_3_14_0~33
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c007cf5db9bda048d78480f60e809313a95b26c9;p=thirdparty%2Fvalgrind.git

Mention --keep-debuginfo=yes in the FAQ for unloaded shared objects.
---

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).</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