Finalise for 1.9.6.
MERGE TO STABLE
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1618 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/FAQ.txt b/FAQ.txt
index 700085a..ee821d2 100644
--- a/FAQ.txt
+++ b/FAQ.txt
@@ -1,8 +1,8 @@
A mini-FAQ for valgrind, version 1.9.6
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Last revised 22 Apr 2003
-~~~~~~~~~~~~~~~~~~~~~~~~
+Last revised 5 May 2003
+~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------------------------------------------
@@ -137,6 +137,10 @@
does not kick in. We would be interested in hearing more
feedback on this.
+ Another possible cause is that versions prior to 1.9.6
+ did not support threading on glibc 2.3.X systems well.
+ Hopefully the situation is much improved with 1.9.6.
+
-----------------------------------------------------------------
Q8. My program dies (exactly) like this:
@@ -145,11 +149,12 @@
valgrind: the `impossible' happened:
Unhandled REPE case
-A8. Yeah ... that I believe is a P4 specific instruction. Are you
- building your app with -march=pentium4 or something like that?
- Others have reported that removing the flag works around this.
- In fact this is pretty easy to fix and I do have it on my
- to-do-for-1.9.6 list.
+A8. Yeah ... that I believe is a SSE or SSE2 instruction. Are you
+ building your app with -march=pentium4 or -march=athlon or
+ something like that? If you can somehow dissuade gcc from
+ producing SSE/SSE2 instructions, you may be able to avoid this.
+ Some folks have reported that removing the flag -march=...
+ works around this.
I'd be interested to hear if you can get rid of it by changing
your application build flags.
@@ -159,35 +164,8 @@
Q9. My program dies complaining that __libc_current_sigrtmin
is unimplemented.
-A9. Try the following. It is an experiment, but it might work.
- We would very much appreciate you telling us if it does/
- does not work for you.
-
- In vg_libpthread.c, add the 3 functions below.
-
- In vg_libpthread_unimp.c, remove the stubs for the same 3
- functions.
-
- Let me know if it helps. Quite a lot of other valgrind users
- complain about this, but I have never been able to reproduce it,
- so fixing it isn't easy. So it's useful if you can try.
-
- int __libc_current_sigrtmin (void)
- {
- return -1;
- }
-
- int __libc_current_sigrtmax (void)
- {
- return -1;
- }
-
- int __libc_allocate_rtsig (int high)
- {
- return -1;
- }
-
- (Note: this fix is already in version 1.9.6 and later)
+A9. Should be fixed in 1.9.6. I would appreciate confirmation
+ of that.
-----------------------------------------------------------------
@@ -199,6 +177,9 @@
this under consideration. Avoid Red Hat >= 8.1 for
the time being, if you can.
+ 5 May 03: 1.9.6 should be significantly improved on
+ Red Hat 9, SuSE 8.2 and other glibc-2.3.2 systems.
+
-----------------------------------------------------------------
Q11. I really need to use the NVidia libGL.so in my app.
@@ -231,14 +212,8 @@
environment variables, possibly including zeroing them
all. Avoid this if you can.
- In any case, you may be able to work around it like this:
- Comment out the
- call to VG_(core_panic) at coregrind/vg_main.c:1647 and see
- if that helps. The text of coregrind/vg_main.c:1647 is as follows:
-
- VG_(core_panic)("VG_(mash_LD_PRELOAD_and_LD_LIBRARY_PATH) failed\n");
-
- and so it's this call you want to comment out.
+ 1.9.6 contains a fix which hopefully reduces the chances
+ of your program bombing out like this.
-----------------------------------------------------------------