/usr/share/doc/wine-doc/html/winedev/dbg-others.htm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Other debuggers</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Wine Developer's Guide"
HREF="index.htm"><LINK
REL="UP"
TITLE="Debugging Wine"
HREF="debugger.htm"><LINK
REL="PREVIOUS"
TITLE="WineDbg Command Reference"
HREF="dbg-commands.htm"><LINK
REL="NEXT"
TITLE="Debug Logging"
HREF="debugging.htm"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="winedoc.css"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Wine Developer's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="dbg-commands.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. Debugging Wine</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="debugging.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="DBG-OTHERS"
>1.8. Other debuggers</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN977"
>1.8.1. GDB mode</A
></H2
><P
>	  WineDbg can act as a remote monitor for GDB.  This allows to
	  use all the power of GDB, but while debugging wine and/or
	  any Win32 application.  To enable this mode, just add
	  <CODE
CLASS="PARAMETER"
>--gdb</CODE
> to winedbg command line.  You'll
	  end up on a GDB prompt.  You'll have to use the GDB commands
	  (not WineDbg's).
	</P
><P
>	  However, some limitation in GDB while debugging wine (see
	  below) don't appear in this mode:
	  <P
></P
><UL
><LI
><P
>		GDB will correctly present Win32 thread
		information and breakpoint behavior
	      </P
></LI
><LI
><P
>		Moreover, it also provides support for the Dwarf II
		debug format (which became the default format (instead
		of stabs) in gcc 3.1).
	      </P
></LI
></UL
>
	</P
><P
>	  A few Wine extensions available through the monitor command.
	  <DIV
CLASS="TABLE"
><A
NAME="AEN988"
></A
><P
><B
>Table 1-12. WineDbg's debug channels' management</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><TBODY
><TR
><TD
><B
CLASS="COMMAND"
>monitor&nbsp;wnd</B
></TD
><TD
>lists all window in the Wine session</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>monitor&nbsp;proc</B
></TD
><TD
>		    lists all processes in the Wine session
		  </TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>monitor&nbsp;mem</B
></TD
><TD
>		    displays memory mapping of debugged process
		  </TD
></TR
></TBODY
></TABLE
></DIV
>
	</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1004"
>1.8.2. Graphical frontends to gdb</A
></H2
><P
>          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.
        </P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1007"
>1.8.2.1. DDD</A
></H3
><P
>            Use the following steps, in this order:
	    <P
></P
><OL
TYPE="1"
><LI
><P
>		  Start the Wine debugger with a command line like:
<PRE
CLASS="SCREEN"
>	winedbg --gdb --no-start &lt;name_of_exe_to_debug.exe&gt;</PRE
>
		</P
></LI
><LI
><P
>                  Start ddd
                </P
></LI
><LI
><P
>		  In ddd, use the 'Open File' or 'Open Program' to
                  point to the Wine executable (which is either
		  wine-pthread or wine-kthread depending on your
		  settings).
		</P
></LI
><LI
><P
>		  In the output of 1/, there's a line like 
<PRE
CLASS="SCREEN"
>	target remote localhost:32878</PRE
>
		  copy that line and paste into ddd command pane (the
		  one with the (gdb) prompt)
		</P
></LI
></OL
>
	    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
          </P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1021"
>1.8.2.2. kdbg</A
></H3
><P
>            Use the following steps, in this order:
            <P
></P
><OL
TYPE="1"
><LI
><P
>                  Start the Wine debugger with a command line like:
<PRE
CLASS="SCREEN"
>	winedbg --gdb --no-start &lt;name_of_exe_to_debug.exe&gt;</PRE
></P
></LI
><LI
><P
>		  In the output of 1/, there's a line like 
<PRE
CLASS="SCREEN"
>	target remote localhost:32878</PRE
>
		  Start kdbg with
<PRE
CLASS="SCREEN"
>kdbg -r localhost:32878 wine</PRE
>
		  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 (which is either
		  wine-pthread or wine-kthread depending on your settings).
		</P
></LI
></OL
>
	    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
          </P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1032"
>1.8.3. Using other Unix debuggers</A
></H2
><P
>          You can also use other debuggers (like
          <B
CLASS="COMMAND"
>gdb</B
>), but you must be aware of a few
          items:
        </P
><P
>          You need to attach the unix debugger to the correct unix
          process (representing the correct windows thread) (you can
          "guess" it from a <B
CLASS="COMMAND"
>ps fax</B
> for example:
          When running the emulator, usually the first two
          <CODE
CLASS="VARNAME"
>upids</CODE
> are for the Windows' application
          running the desktop, the first thread of the application is
          generally the third <CODE
CLASS="VARNAME"
>upid</CODE
>; when running a
          Winelib program, the first thread of the application is
          generally the first <CODE
CLASS="VARNAME"
>upid</CODE
>)
        </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>	    If you plan to used <B
CLASS="COMMAND"
>gdb</B
> for a
	    multi-threaded Wine application (native or Winelib), then
	    <B
CLASS="COMMAND"
>gdb</B
> will be able to handle the multiple
	    threads directly only if:
	    <P
></P
><UL
><LI
><P
>		  Wine is running on the pthread model (it won't work
		  in the kthread one).  See the Wine architecture
		  documentation for further details.
		</P
></LI
><LI
><P
>		  <B
CLASS="COMMAND"
>gdb</B
> supports the multi-threading
		  (you need gdb at least 5.0 for that).
		</P
></LI
></UL
>
	    In the unfortunate case (no direct thread support in
	    <B
CLASS="COMMAND"
>gdb</B
> because one of the above conditions
	    is false), you'll have to spawn a different
	    <B
CLASS="COMMAND"
>gdb</B
> session for each Windows' thread
	    you wish to debug (which means no synchronization for
	    debugging purposes between the various threads).
          </P
></BLOCKQUOTE
></DIV
><P
>          Here's how to get info about the current execution status of a
          certain Wine process:
        </P
><P
>          Change into your Wine source dir and enter:
        </P
><PRE
CLASS="SCREEN"
>$ gdb wine
        </PRE
><P
>          Switch to another console and enter <B
CLASS="COMMAND"
>ps ax | grep
            wine</B
> to find all wine processes.  Inside
          <B
CLASS="COMMAND"
>gdb</B
>, repeat for all Wine processes:
        </P
><PRE
CLASS="SCREEN"
>(gdb) attach <KBD
CLASS="USERINPUT"
>PID</KBD
>
        </PRE
><P
>          with <KBD
CLASS="USERINPUT"
>PID</KBD
> being the process ID of one of
          the Wine processes.  Use
        </P
><PRE
CLASS="SCREEN"
>(gdb) bt
        </PRE
><P
>          to get the backtrace of the current Wine process, i.e. the
          function call history.  That way you can find out what the
          current process is doing right now.  And then you can use
          several times:
        </P
><PRE
CLASS="SCREEN"
>(gdb) n
        </PRE
><P
>          or maybe even
        </P
><PRE
CLASS="SCREEN"
>(gdb) b <KBD
CLASS="USERINPUT"
>SomeFunction</KBD
>
        </PRE
><P
>          and
        </P
><PRE
CLASS="SCREEN"
>(gdb) c
        </PRE
><P
>          to set a breakpoint at a certain function and continue up to
          that function.  Finally you can enter
        </P
><PRE
CLASS="SCREEN"
>(gdb) detach
        </PRE
><P
>          to detach from the Wine process.
        </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1074"
>1.8.4. Using other Windows debuggers</A
></H2
><P
>          You can use any Windows' debugging API compliant debugger
          with Wine.  Some reports have been made of success with
          VisualStudio debugger (in remote mode, only the hub runs
          in Wine).  GoVest fully runs in Wine.
        </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1077"
>1.8.5. Main differences between winedbg and regular Unix debuggers</A
></H2
><DIV
CLASS="TABLE"
><A
NAME="AEN1079"
></A
><P
><B
>Table 1-13. Debuggers comparison</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><TBODY
><TR
><TD
>WineDbg</TD
><TD
>gdb</TD
></TR
><TR
><TD
>		  WineDbg debugs a Windows' process: the various
		  threads will be handled by the same WineDbg session,
		  and a breakpoint will be triggered for any thread of
		  the W-process 
                </TD
><TD
>		  gdb debugs a Windows' thread: a separate gdb session
		  is needed for each thread of a Windows' process and
		  a breakpoint will be triggered only for the w-thread
		  debugged 
                </TD
></TR
><TR
><TD
>		  WineDbg supports debug information from stabs
		  (standard Unix format) and Microsoft's C, CodeView,
		  .DBG
                </TD
><TD
>		  GDB supports debug information from stabs (standard
		  Unix format) and Dwarf II.
                </TD
></TR
></TBODY
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="dbg-commands.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.htm"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="debugging.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>WineDbg Command Reference</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="debugger.htm"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Debug Logging</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
wine-doc 1.0.0-1 / usr / share / doc / wine-doc / html / winedev / dbg-others.htm
