</para>
</listitem>
+ <listitem>
+ <para>Registers values.</para>
+ <para>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 <option>--vex-iropt-precise-memory-exns=yes</option>
+ ensures precise registers values by disabling some optimisations.
+ </para>
+ </listitem>
+
<listitem>
<para>Hardware watchpoint support by the Valgrind
gdbserver.</para>
<option><![CDATA[--vgdb=<no|yes|full> [default: yes] ]]></option>
</term>
<listitem>
+
<para>Valgrind will provide "gdbserver" functionality when
- <option>--vgdb=yes</option>
- or <option>--vgdb=full</option> is specified. This
- allows an external GNU GDB debugger
- to control and debug your program when it runs on Valgrind. See
- <xref linkend="manual-core-adv.gdbserver"/> for a detailed
- description.
+ <option>--vgdb=yes</option> or <option>--vgdb=full</option> is
+ specified. This allows an external GNU GDB debugger to control
+ and debug your program when it runs on Valgrind.
+ <option>--vgdb=full</option> incurs significant performance
+ overheads, but provides more precise breakpoints and
+ watchpoints. See <xref linkend="manual-core-adv.gdbserver"/> for
+ a detailed description.
</para>
<para> If the embedded gdbserver is enabled but no gdb is
documented in the tool specific chapter.
</para>
- <para><option>--vgdb=full</option> incurs
- significant performance overheads.
- </para>
</listitem>
</varlistentry>