Added FAQ 15, about writing to read-only memory.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1795
This commit is contained in:
Nicholas Nethercote 2003-08-07 21:24:24 +00:00
parent 568fcc200b
commit 37f6cc0c0d

15
FAQ.txt
View File

@ -328,4 +328,19 @@ A14. First of all: relax, it's probably not a bug, but a feature.
-----------------------------------------------------------------
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.)