winedbg doc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Added some details about running kdbg and ddd with winedbg (in gdb proxy mode), for the ones who like graphical debuggers instead of text oriented ones.

A+
--
Eric Pouech
Title: Graphical frontends to gdb
Name: grgdb ChangeLog: added a section about using kgdb and ddd to debug wine License: X11 GenDate: 2003/06/18 20:04:44 UTC ModifiedFiles: documentation/debugger.sgml =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/documentation/debugger.sgml,v retrieving revision 1.21 diff -u -u -r1.21 debugger.sgml --- documentation/debugger.sgml 18 Jun 2003 03:30:40 -0000 1.21 +++ documentation/debugger.sgml 18 Jun 2003 06:01:48 -0000 @@ -1565,6 +1565,87 @@ + + + + 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

[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux