This wasn't supposed to be part of r10701.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10702

diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml
index 07f3f1a5d5a758b39c44a220fe6ddc85ab7a617b..22409a4119bae1e7bdef0e9c3e61251c6dea9e5c 100644 (file)
--- a/docs/xml/FAQ.xml
+++ b/docs/xml/FAQ.xml
@@ -182,29 +182,6 @@ collect2: ld returned 1 exit status
   </answer>
 </qandaentry>
 
-<qandaentry id="faq.bss">
-  <question id="q-bss">
-    <para>My program fails to start, and this message is printed:</para>
-<screen></screen>
-  </question>
-  <answer id="a-bss">
-    <para>One possibility is that your program has a bug and erroneously
-    jumps to a non-code address, in which case you'll get a SIGILL signal.
-    Memcheck may issue a warning just before this happens, but it might not
-    if the jump happens to land in addressable memory.</para>
-
-    <para>Another possibility is that Valgrind does not handle the
-    instruction.  If you are using an older Valgrind, a newer version might
-    handle the instruction.  However, all instruction sets have some
-    obscure, rarely used instructions.  Also, on amd64 there are an almost
-    limitless number of combinations of redundant instruction prefixes, many
-    of them undocumented but accepted by CPUs.  So Valgrind will still have
-    decoding failures from time to time.  If this happens, please file a bug
-    report.</para>
-
-  </answer>
-</qandaentry>
-
 <qandaentry id="faq.java">
   <question id="q-java">
     <para>I tried running a Java program (or another program that uses a