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

diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml
index 47adf6b20decd027cb1ffed68619d1ddf3b95183..d0d917edceaff15a2a7e5d3dbea795e9d42d799e 100644 (file)
--- 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