Eric Pouech wrote:
Switch to UNIX shell, get the process-ID using ps -a | grep wine, and
do a kill -HUP <pid> (without the < and >). Wine will then enter its
internal debugger and you can proceed as explained above. Also, you
can use --debug switch and then you can get into internal debugger by
pressing Ctrl-C in the terminal where you run Wine.
the Ctrl-C should be working (if you did start the program under
winedbg)
A+
How is this instead then?
Change Log: Update debugger documentation for when programs hangs.
Files: debugger.sgml
--
Tony Lambregts
Index: debugger.sgml
===================================================================
RCS file: /home/wine/wine/documentation/debugger.sgml,v
retrieving revision 1.14
diff -u -r1.14 debugger.sgml
--- debugger.sgml 30 Nov 2002 01:57:19 -0000 1.14
+++ debugger.sgml 7 Dec 2002 06:26:58 -0000
@@ -430,16 +430,12 @@
<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
- <pid></command> (without the < 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 @@
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
