From: Julian Seward <jseward@acm.org>
Date: Tue, 14 Oct 2003 07:30:33 +0000 (+0000)
Subject: Mention that -fno-inline is a helpful build flag when you're debugging.
X-Git-Tag: svn/VALGRIND_2_1_0~137
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3cab8f4f8e64f34af6c252bd0660ac0307ec2eef;p=thirdparty%2Fvalgrind.git

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 5e9c876e9b..0ef41d6137 100644
--- 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