From: Philippe Waroquiers Date: Tue, 24 Jul 2012 20:24:39 +0000 (+0000) Subject: Better document the limitation of gdbsrv for registers and flags values X-Git-Tag: svn/VALGRIND_3_8_0~90 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=668df8d0067137bc56b6d1cce3665b449b2dd111;p=thirdparty%2Fvalgrind.git Better document the limitation of gdbsrv for registers and flags values During investigations of 303963, Josef found that flags are not always up to date and that --vex-guest-max-insns=1 ensures flags values are (more?) correct. => enhance the paragraph in the gdbserver limitations to reference this option and give an idea of the performance impact of the other options helping to increase the precision of registers and flags. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12778 --- diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml index fe00ac1901..73179b568c 100644 --- a/docs/xml/manual-core-adv.xml +++ b/docs/xml/manual-core-adv.xml @@ -784,12 +784,24 @@ are however some limitations and peculiarities: - Registers values. - When Valgrind gdbserver stops on an error, registers values - might not be always up to date due to the optimisations done by - the Valgrind core. The - option - ensures precise registers values by disabling some optimisations. + Processor registers and flags values. + When Valgrind gdbserver stops on an error, on a breakpoint + or when single stepping, registers and flags values might not be always + up to date due to the optimisations done by the Valgrind core. + Disabling some optimisations using the following options will increase + the precision of registers and flags values. + An idea of the performance impact for memcheck is given for each option. + + + (10% performance impact). + + + (200% performance impact). + + + (250% performance impact). + +