From: Philippe Waroquiers Date: Mon, 2 Jan 2023 22:04:44 +0000 (+0100) Subject: Small improvement to documentation. X-Git-Tag: VALGRIND_3_21_0~244 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=56971834a79eff2decd16cdb23f16a2d4d37181a;p=thirdparty%2Fvalgrind.git Small improvement to documentation. --- diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml index 1fa801edc1..6991a95e06 100644 --- a/docs/xml/manual-core-adv.xml +++ b/docs/xml/manual-core-adv.xml @@ -308,9 +308,9 @@ tool-specific macros). xreflabel="&vg-gdbserver-label;"> Debugging your program using Valgrind gdbserver and GDB -A program running under Valgrind is not executed directly by the -CPU. Instead it runs on a synthetic CPU provided by Valgrind. This is -why a debugger cannot debug your program when it runs on Valgrind. +A program running under Valgrind is not executed directly by the CPU. +Instead it runs on a synthetic CPU provided by Valgrind. This is why a debugger +cannot natively debug your program when it runs on Valgrind. This section describes how GDB can interact with the