commit 0a970ce0e28eac58fd7adeadb094eeb4c0025d66
author Eric Pouech <pouech-eric@wanadoo.fr> Fri Jun 20 21:27:27 2003 +0000
committer Alexandre Julliard <julliard@winehq.org> Fri Jun 20 21:27:27 2003 +0000
tree 2ba55c6c6b5d146a4a0a9f78b0c7984742354125
parent 90b1c2cd52883f4d57f0f3cf68bbc54c94342aa5

Added a section about using kgdb and ddd to debug wine.

documentation/debugger.sgml

diff --git a/documentation/debugger.sgml b/documentation/debugger.sgml
index 7b1e7bf..d9d3298 100644
--- a/documentation/debugger.sgml
+++ b/documentation/debugger.sgml
@@ -1565,6 +1565,87 @@
       </sect2>
 
       <sect2>
+	<title>Graphical frontends to gdb</title>
+
+	<para>
+          This section will describe how you can debug wine using the
+          GDB mode of winedbg and some graphical front ends to GDB for
+          those of you who really like graphical debuggers.
+        </para>
+
+	<sect3>
+	  <title>DDD</title>
+	  
+	  <para>
+            Use the following steps, in this order:
+<orderedlist>
+	      <listitem>
+		<para>
+Start the wine debugger with a command line
+like:
+<screen>
+	winedbg -- --gdb --no-start &lt;name_of_exe_to_debug.exe&gt;
+</screen>
+</para>
+	      </listitem>
+	      <listitem>
+		<para>Start ddd</para>
+	      </listitem>
+	      <listitem>
+		<para>In ddd, use the 'Open File' or 'Open Program' to
+                  point to the wine executable</para>
+	      </listitem>
+	      <listitem>
+		<para>In the output of 1/, there's a line like 
+<screen>
+	target remote localhost:32878
+</screen>
+copy that line and paste into ddd command pane (the one with the (gdb)
+prompt)
+</para>
+	      </listitem>
+	    </orderedlist>
+The program should now be loaded and up and running. If you want, you
+can also add in 1/ after the name of the exec all the needed
+parameters
+          </para>
+	</sect3>
+	<sect3>
+	  <title>kdbg</title>
+	  
+	  <para>
+            Use the following steps, in this order:
+            <orderedlist>
+	      <listitem>
+		<para>
+                  Start the wine debugger with a command line like:
+<screen>
+	winedbg -- --gdb --no-start &lt;name_of_exe_to_debug.exe&gt;
+</screen>
+</para>
+	      </listitem>
+	      <listitem>
+		<para>In the output of 1/, there's a line like 
+<screen>
+	target remote localhost:32878
+</screen>
+Start kdbg with
+<screen>
+kdbg -r localhost:32878 wine
+</screen>
+localhost:32878 is not a fixed value, but has been printed in step
+1/. 'wine' should also be the full path to the wine executable.
+</para>
+	      </listitem>
+	    </orderedlist>
+The program should now be loaded and up and running. If you want, you
+can also add in 1/ after the name of the exec all the needed
+parameters
+          </para>
+	</sect3>
+      </sect2>
+	
+      <sect2>
         <title>Using other Unix debuggers</title>
 
         <para>