mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-09 05:10:23 +00:00
21ceb09d5d
Otherwise xsltproc will complain while producing the manpage that it doesn't know how to interpret the release string.
90 lines
2.3 KiB
XML
90 lines
2.3 KiB
XML
<?xml version="1.0"?> <!-- -*- sgml -*- -->
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"
|
|
[ <!ENTITY % vg-entities SYSTEM "../../docs/xml/vg-entities.xml"> %vg-entities; ]>
|
|
|
|
|
|
<refentry id="vgdb">
|
|
|
|
<refmeta>
|
|
<refentrytitle>vgdb</refentrytitle>
|
|
<manvolnum>1</manvolnum>
|
|
<refmiscinfo class="version">Release &rel-version;</refmiscinfo>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>vgdb</refname>
|
|
<refpurpose>intermediary between Valgrind and GDB or a shell</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsynopsisdiv>
|
|
<cmdsynopsis>
|
|
<command>vgdb</command>
|
|
<arg><replaceable>options</replaceable></arg>
|
|
</cmdsynopsis>
|
|
</refsynopsisdiv>
|
|
|
|
|
|
<refsect1 id="vgdb-description">
|
|
<title>Description</title>
|
|
|
|
<para><command>vgdb</command> ("Valgrind to GDB") is used as an
|
|
intermediary between Valgrind and GDB or a shell. It has two usage modes:
|
|
</para>
|
|
|
|
<xi:include href="../../docs/xml/manual-core-adv.xml"
|
|
xpointer="vgdb.desc.modes"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude" />
|
|
|
|
</refsect1>
|
|
|
|
<refsect1 id="vgdb-options">
|
|
<title>Options</title>
|
|
|
|
<xi:include href="../../docs/xml/manual-core-adv.xml"
|
|
xpointer="vgdb.opts.list"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude" />
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1 id="vgdb-see_also">
|
|
<title>See Also</title>
|
|
|
|
<para>
|
|
valgrind(1),
|
|
<filename>&vg-docs-path;</filename> or
|
|
<filename>&vg-docs-url;</filename>,
|
|
<!-- Note that the ids used have vgdb- prefixed. This is because the same
|
|
ids are used in the valgrind.1 man page. That conflict even though
|
|
the valgrind.1 and vgdb.1 manual page are generated separately. It
|
|
still works fine, since in vgdb the references are only direct in this
|
|
"See Also" refsect. The labels and urls still come out as intended. -->
|
|
<ulink id="vgdb-&vg-gdbserver-id;"
|
|
xreflabel="&vg-gdbserver-label;"
|
|
url="&vg-gdbserver-url;">&vg-gdbserver-label;</ulink>
|
|
<ulink id="vgdb-&vg-vgdb-id;"
|
|
xreflabel="&vg-vgdb-label;"
|
|
url="&vg-vgdb-url;">&vg-vgdb-label;</ulink>,
|
|
<ulink id="vgdb-&vg-monitor-id;"
|
|
xreflabel="&vg-monitor-label;"
|
|
url="&vg-monitor-url;">&vg-monitor-label;</ulink>.
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
|
<refsect1 id="vgdb-author">
|
|
<title>Author</title>
|
|
|
|
<para>Philippe Waroquiers.</para>
|
|
|
|
</refsect1>
|
|
|
|
|
|
</refentry>
|
|
|
|
|