Update FAQ about GLIBCXX_FORCE_NEW name-change.

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

diff --git a/FAQ.txt b/FAQ.txt
index 855286aaafee98f20669b7e8e27440d263d5ae05..625c55cb428cd4f727d644c719ddefce12444d3e 100644 (file)
--- a/FAQ.txt
+++ b/FAQ.txt
@@ -169,9 +169,12 @@ so will probably slow down your program, sometimes drastically.
   with -D__USE_MALLOC. Beware! This is removed from gcc starting with
   version 3.3.
 
-- With 3.2.2 and later, you should export the environment variable
+- With gcc 3.2.2 and later, you should export the environment variable
   GLIBCPP_FORCE_NEW before running your program.
 
+- With gcc 3.4 and later, that variable has changed name to
+  GLIBCXX_FORCE_NEW.
+
 There are other ways to disable memory pooling: using the malloc_alloc
 template with your objects (not portable, but should work for gcc) or
 even writing your own memory allocators. But all this goes beyond the

diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml
index ff8c087b185ad2d7f0f593c954d5a41a90997e2c..fed9275c6d36fd5390b65011705d9c3a8d1fd832 100644 (file)
--- a/docs/xml/FAQ.xml
+++ b/docs/xml/FAQ.xml
@@ -234,10 +234,14 @@
     This is removed from gcc starting with version 3.3.</para>
    </listitem>
    <listitem>
-    <para>With 3.2.2 and later, you should export the environment
+    <para>With gcc 3.2.2 and later, you should export the environment
     variable <literal>GLIBCPP_FORCE_NEW</literal> before running
     your program.</para>
    </listitem>
+   <listitem>
+    <para>With gcc 3.4 and later, that variable has changed name to
+    <literal>GLIBCXX_FORCE_NEW</literal>.</para>
+   </listitem>
   </itemizedlist>
 
   <para>There are other ways to disable memory pooling: using the