Added FAQ 15, about writing to read-only memory.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1795 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/FAQ.txt b/FAQ.txt
index ee821d2..376010a 100644
--- a/FAQ.txt
+++ b/FAQ.txt
@@ -328,4 +328,19 @@
-----------------------------------------------------------------
+Q15. My program dies with a segmentation fault, but Valgrind doesn't give
+ any error messages before it, or none that look related.
+
+A15. The one kind of segmentation fault that Valgrind won't give any
+ warnings about is writes to read-only memory. Maybe your program is
+ writing to a static string like this:
+
+ char* s = "hello";
+ s[0] = 'j';
+
+ or something similar. Writing to read-only memory can also apparently
+ make LinuxThreads behave strangely.
+
+-----------------------------------------------------------------
+
(this is the end of the FAQ.)