From: Nicholas Nethercote <n.nethercote@gmail.com>
Date: Sun, 18 Jul 2004 10:35:36 +0000 (+0000)
Subject: Extra info for FAQ.
X-Git-Tag: svn/VALGRIND_2_1_2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=02a2002701ce104815137fe4ab536dfdd69e5522;p=thirdparty%2Fvalgrind.git

Extra info for FAQ.


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

diff --git a/FAQ.txt b/FAQ.txt
index 80442bc9ea..26a31d67df 100644
--- a/FAQ.txt
+++ b/FAQ.txt
@@ -1,6 +1,6 @@
 Valgrind FAQ, version 2.1.2
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Last revised 6 April 2004
+Last revised 18 July 2004
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 1. Background
@@ -117,9 +117,14 @@ Older versions did not support some x86 instructions, particularly
 SSE/SSE2 instructions.  Try a newer Valgrind;  we now support almost all
 instructions.  If it still happens with newer versions, if the failing
 instruction is an SSE/SSE2 instruction, you might be able to recompile
-your progrma without it by using the flag -march to gcc.  Either way,
+your program without it by using the flag -march to gcc.  Either way,
 let us know and we'll try to fix it.
 
+Another 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/Addrcheck may issue a warning just before this happens, but they
+might not if the jump happens to land in addressable memory.
+
 -----------------------------------------------------------------
 
 3.4. My program dies like this: