|
From: Philippe W. <phi...@so...> - 2023-01-02 22:06:36
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=56971834a79eff2decd16cdb23f16a2d4d37181a commit 56971834a79eff2decd16cdb23f16a2d4d37181a Author: Philippe Waroquiers <phi...@sk...> Date: Mon Jan 2 23:04:44 2023 +0100 Small improvement to documentation. Diff: --- docs/xml/manual-core-adv.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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).</para> xreflabel="&vg-gdbserver-label;"> <title>Debugging your program using Valgrind gdbserver and GDB</title> -<para>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. +<para>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. </para> <para> This section describes how GDB can interact with the |