diff --git a/documentation/debugger.sgml b/documentation/debugger.sgml
index 7b1e7bff9bf..d9d3298309a 100644
--- a/documentation/debugger.sgml
+++ b/documentation/debugger.sgml
@@ -1564,6 +1564,87 @@ monitor mem displays memory mapping of debugged process
+
+ Graphical frontends to gdb
+
+
+ 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.
+
+
+
+ DDD
+
+
+ Use the following steps, in this order:
+
+
+
+Start the wine debugger with a command line
+like:
+
+ winedbg -- --gdb --no-start <name_of_exe_to_debug.exe>
+
+
+
+
+ Start ddd
+
+
+ In ddd, use the 'Open File' or 'Open Program' to
+ point to the wine executable
+
+
+ In the output of 1/, there's a line like
+
+ target remote localhost:32878
+
+copy that line and paste into ddd command pane (the one with the (gdb)
+prompt)
+
+
+
+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
+
+
+
+ kdbg
+
+
+ Use the following steps, in this order:
+
+
+
+ Start the wine debugger with a command line like:
+
+ winedbg -- --gdb --no-start <name_of_exe_to_debug.exe>
+
+
+
+
+ In the output of 1/, there's a line like
+
+ target remote localhost:32878
+
+Start kdbg with
+
+kdbg -r localhost:32878 wine
+
+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.
+
+
+
+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
+
+
+
+
Using other Unix debuggers