Document that --read-inline-info=yes is the default

even on Solaris for Memcheck, Helgrind and DRD.
n-i-bz

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

diff --git a/coregrind/m_main.c b/coregrind/m_main.c
index afe69ad7339e7e7979c455095f4ae6df4a9190f9..1821c9412fa7a7f2a12a7262cfb2663534c64d6d 100644 (file)
--- a/coregrind/m_main.c
+++ b/coregrind/m_main.c
@@ -166,7 +166,7 @@ static void usage_NORETURN ( Bool debug_help )
 "                              code except that from file-backed mappings\n"
 "    --read-inline-info=yes|no read debug info about inlined function calls\n"
 "                              and use it to do better stack traces.  [yes]\n"
-"                              on Linux/Android for Memcheck/Helgrind/DRD\n"
+"                              on Linux/Android/Solaris for Memcheck/Helgrind/DRD\n"
 "                              only.  [no] for all other tools and platforms.\n"
 "    --read-var-info=yes|no    read debug info on stack and global variables\n"
 "                              and use it to print better error messages in\n"

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index e384550262d4cb41bac02dc6ec3d4a6b6b6bc467..edda8a1e43237c4f89b5e577a05f976c2ed21e10 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -1771,8 +1771,8 @@ need to use them.</para>
       startup and makes it use more memory (typically for each inlined
       piece of code, 6 words and space for the function name), but it
       results in more descriptive stacktraces.  For the 3.10.0
-      release, this functionality is enabled by default only for Linux
-      and Android targets and only for the tools Memcheck, Helgrind
+      release, this functionality is enabled by default only for Linux,
+      Android and Solaris targets and only for the tools Memcheck, Helgrind
       and DRD.  Here is an example of some stacktraces with
       <option>--read-inline-info=no</option>:
 </para>

diff --git a/none/tests/cmdline1.stdout.exp b/none/tests/cmdline1.stdout.exp
index e698ad1d221a6ac7559bedef800369e23956e6da..cc25a16b961a89d587c70940a436958babca48a6 100644 (file)
--- a/none/tests/cmdline1.stdout.exp
+++ b/none/tests/cmdline1.stdout.exp
@@ -80,7 +80,7 @@ usage: valgrind [options] prog-and-args
                               code except that from file-backed mappings
     --read-inline-info=yes|no read debug info about inlined function calls
                               and use it to do better stack traces.  [yes]
-                              on Linux/Android for Memcheck/Helgrind/DRD
+                              on Linux/Android/Solaris for Memcheck/Helgrind/DRD
                               only.  [no] for all other tools and platforms.
     --read-var-info=yes|no    read debug info on stack and global variables
                               and use it to print better error messages in

diff --git a/none/tests/cmdline2.stdout.exp b/none/tests/cmdline2.stdout.exp
index ca948a8577cec33a21129d19eb3f44dc03fe9507..580fa1968052ccd0d25ae08e7720d6e32f599896 100644 (file)
--- a/none/tests/cmdline2.stdout.exp
+++ b/none/tests/cmdline2.stdout.exp
@@ -80,7 +80,7 @@ usage: valgrind [options] prog-and-args
                               code except that from file-backed mappings
     --read-inline-info=yes|no read debug info about inlined function calls
                               and use it to do better stack traces.  [yes]
-                              on Linux/Android for Memcheck/Helgrind/DRD
+                              on Linux/Android/Solaris for Memcheck/Helgrind/DRD
                               only.  [no] for all other tools and platforms.
     --read-var-info=yes|no    read debug info on stack and global variables
                               and use it to print better error messages in