Mention that -fno-inline is a helpful build flag when you're debugging.

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

diff --git a/coregrind/docs/coregrind_core.html b/coregrind/docs/coregrind_core.html
index 5e9c876e9b647975166b48a25266e9627d2a8ce2..0ef41d6137fb7aff3386b2eec470a7530ffc0d38 100644 (file)
--- a/coregrind/docs/coregrind_core.html
+++ b/coregrind/docs/coregrind_core.html
@@ -95,6 +95,13 @@ belongs to, which makes both error messages and profiling output
 nearly useless.  With <code>-g</code>, you'll hopefully get messages
 which point directly to the relevant source code lines.
 
+<p>
+Another flag you might like to consider, if you are working with 
+C++, is <code>-fno-inline</code>.  That makes it easier to see the
+function-call chain, which can help reduce confusion when navigating
+around large C++ apps.  For whatever it's worth, debugging
+OpenOffice.org with Valgrind is a bit easier when using this flag.
+
 <p>
 You don't have to do this, but doing so helps Valgrind produce more
 accurate and less confusing error reports.  Chances are you're set up