Update FAQ about GLIBCXX_FORCE_NEW name-change.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3678 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/FAQ.txt b/FAQ.txt
index 855286a..625c55c 100644
--- a/FAQ.txt
+++ b/FAQ.txt
@@ -169,9 +169,12 @@
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 ff8c087..fed9275 100644
--- 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