diff options
| author | sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> | 2011-05-17 17:15:07 +0000 |
|---|---|---|
| committer | sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> | 2011-05-17 17:15:07 +0000 |
| commit | d142f99836471d4245250247cc9ac7bc5a1391fa (patch) | |
| tree | d4b9f307a879c49bd848aa8810469ccaf6077b86 /docs | |
| parent | f071e5e0ca87c5d1dac9f05e7ff24a83ee0170e5 (diff) | |
gdbserver: misc fixes (#214909 c 77)
Fix some tests on ppc-debian6,s390x + handled Nick Nethercote, Josef
Weidendorfer comments
* improved testing & related doc
- added option --vex-iropt-precise-memory-exns=yes to mcsig(no)pass.vgtest
+ updated manual-core.xml
- cleanup some comments in *.vgtest
- modified filter_gdb and filter_memcheck_monitor to
handle specific ppc/debian6.0 mcsig(no)pass output
handle specific s390x 'missing debug info'
- added more information in README_DEVELOPPERS on how to
investigate failing gdbserver tests.
* handled Nick Nethercote comment:
Replaced kludgy ms.snapshot detailed
by ms.detailed_snaphot
Updated documentation and test.
* handled Josef Weindendorfer comments:
- do not report an error if ptrace_scope file can't be read.
Instead, a debug trace is done if -d (debug) option given
- added an option -l to give the list of active Valgrind
gdbserver. Useful a.o. to support callgrind_control.
Updated documentation
- added ref. to vgdb help in the vgdb --help message
(Philippe Waroquiers, philippe.waroquiers@skynet.be)
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11770 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/xml/manual-core.xml | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index acc8f73c..368b20be 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -2255,7 +2255,9 @@ Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. <para> Stack unwinding on PPC32/PPC64. </para> <para> On PPC32/PPC64, stack unwinding for leaf functions (i.e. functions not calling other functions) does work properly - only with <option>--vex-iropt-precise-memory-exns=yes</option> + only with <option>--vex-iropt-precise-memory-exns=yes</option>. + You must also pass this option to have a precise stack when + a signal is trapped by gdb. </para> </listitem> @@ -2522,6 +2524,11 @@ vgdb vg.set log_output -c mc.leak_check any shared memory used by the Valgrind gdbserver. vgdb will exit after having shown the Valgrind gdbserver shared memory state.</para> </listitem> + + <listitem> + <para><option>-l</option> instructs vgdb to report the list of + the Valgrind gdbserver processes running and then exit.</para> + </listitem> </itemizedlist> </sect1> |