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

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1921
This commit is contained in:
Julian Seward 2003-10-14 07:30:33 +00:00
parent 43f7ebcc30
commit 3cab8f4f8e

View File

@ -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