ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update debugger documentation for when programs hangs.

This commit is contained in:
Tony Lambregts 2002-12-07 23:48:36 +00:00 committed by Alexandre Julliard
parent 3390547aef
commit 263cdcd88a
1 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
documentation/debugger.sgml
View File

@ -430,16 +430,12 @@ winedbg "hl.exe -windowed"
<title>Program hangs, nothing happens</title>
<para>
<emphasis>Fix me - this is out of date </emphasis>
Switch to UNIX shell, get the process-ID using <command>ps -a |
grep wine</command>, and do a <command>kill -HUP
&lt;pid></command> (without the &lt; and >). Wine will
then enter its internal debugger and you can proceed as
explained above. Also, you can use
<parameter>--debug</parameter> switch and then you can get into
internal debugger by pressing
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo> in
the terminal where you run Wine.
Start the program with <command>winedbg</command> instead of
<command>wine</command>. When the program locks up switch to the
winedbg terminal and press
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>. this
will stop the program and let you debug the program as you would for
a crash.
</para>
</sect2>
@ -664,11 +660,11 @@ wine --debugmsg +relay program
to get a listing of the functions the program calls in its start function.
Now you do a
<programlisting>
wine --debug winfile.exe
winedbg winfile.exe
</programlisting>
</para>
<para>
This way, you get into <command>Wine-dbg</command>. Now you
This way, you get into <command>winedbg</command>. Now you
can set a breakpoint on any function the program calls in
the start function and just type <userinput>c</userinput>
to bypass the eventual calls of Winfile to this function