Small fixes in 'getting started' section of user manual

* Mention --read-inline-info=yes as an alternative to compile without inlining.

* Mention that stabs debuginfo reader is not working anymore since 3.9.0



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

docs/xml/manual-core.xml

@@ -108,7 +108,11 @@ OpenOffice.org with Memcheck is a bit easier when using this option.  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 like this
 already, if you intended to debug your program with GNU GDB, or some
-other debugger.</para>
+other debugger. Alternatively, the Valgrind option 
+<option>--read-inline-info=yes</option> instructs Valgrind to read
+the debug information describing inlining information. With this,
+function call chain will be properly shown, even when your application
+is compiled with inlining. </para>
 
 <para>If you are planning to use Memcheck: On rare
 occasions, compiler optimisations (at <option>-O2</option>
@@ -129,12 +133,9 @@ is also a good idea in general.)  All other tools (as far as we know) are
 unaffected by optimisation level, and for profiling tools like Cachegrind it
 is better to compile your program at its normal optimisation level.</para>
 
-<para>Valgrind understands both the older "stabs" debugging format, used
-by GCC versions prior to 3.1, and the newer DWARF2/3/4 formats
-used by GCC
-3.1 and later.  We continue to develop our debug-info readers,
-although the majority of effort will naturally enough go into the newer
-DWARF readers.</para>
+<para>Valgrind understands the DWARF2/3/4 formats used by GCC 3.1 and
+later.  The reader for "stabs" debugging format (used by GCC versions
+prior to 3.1) has been disabled in Valgrind 3.9.0.</para>
 
 <para>When you're ready to roll, run Valgrind as described above.
 Note that you should run the real