Docu: mention piping for debugmsgs
Andreas Mohr
andi at rhlx01.fht-esslingen.de
Sat Apr 24 15:25:18 CDT 2004
Hi all,
ok, another patch:
Make people know how to reduce log size, using pipes.
Andreas Mohr
-------------- next part --------------
Determining best CVS host...
Using CVSROOT :pserver:cvs at rhlx01.fht-esslingen.de:/home/wine
Index: documentation/debugging.sgml
===================================================================
RCS file: /home/wine/wine/documentation/debugging.sgml,v
retrieving revision 1.14
diff -u -r1.14 debugging.sgml
--- documentation/debugging.sgml 20 Apr 2004 20:16:54 -0000 1.14
+++ documentation/debugging.sgml 24 Apr 2004 20:21:55 -0000
@@ -229,6 +229,34 @@
WineDbg Command Reference section for how to do this.
</para>
+ <para>
+ Another way to conditionally log debug output (e.g. in case of
+ very large installers which may create gigabytes of log
+ output) is to create a pipe:
+ </para>
+ <screen>
+ <prompt>$</prompt> <userinput>mknod /tmp/debug_pipe p</userinput>
+ </screen>
+
+ <para>
+ and then to run wine like that:
+ </para>
+ <screen>
+ <prompt>$</prompt> <userinput>wine --debugmsg +relay,+snoop setup.exe &>/tmp/debug_pipe</userinput>
+ </screen>
+
+ <para>
+ Once you are about to approach the problematic part of the program,
+ you just do:
+ </para>
+ <screen>
+ <prompt>$</prompt> <userinput>cat /tmp/debug_pipe >/tmp/wine.log</userinput>
+ </screen>
+ <para>
+ to capture specifically the part that interests you from the
+ pipe without wasting excessive amounts of HDD space and
+ slowing down installation considerably.
+ </para>
<para>
The <parameter>WINEDEBUG</parameter> environment variable
controls the output of the debug messages.
More information about the wine-patches
mailing list