From ab6cd7bdb694744b17e9d3eb6ee1282939509ef5 Mon Sep 17 00:00:00 2001 From: Andreas Mohr Date: Wed, 28 Apr 2004 00:23:48 +0000 Subject: [PATCH] Explain how to reduce log size, using pipes. --- documentation/debugging.sgml | 38 ++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/documentation/debugging.sgml b/documentation/debugging.sgml index d9afae5cc52..d394c607a84 100644 --- a/documentation/debugging.sgml +++ b/documentation/debugging.sgml @@ -229,6 +229,44 @@ HANDLE32 WINAPI YourFunc(LPCSTR s) WineDbg Command Reference section for how to do this. + + 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: + + + $ mknod /tmp/debug_pipe p + + + + and then to run wine like that: + + + $ wine --debugmsg +relay,+snoop setup.exe &>/tmp/debug_pipe + + + + Since the pipe is initially blocking (and thus wine as a whole), + you have to activate it by doing: + + + $ cat /tmp/debug_pipe + + + (press Ctrl-C to stop pasting the pipe content) + + + Once you are about to approach the problematic part of the program, + you just do: + + + $ cat /tmp/debug_pipe >/tmp/wine.log + + + to capture specifically the part that interests you from the + pipe without wasting excessive amounts of HDD space and + slowing down installation considerably. + The WINEDEBUG environment variable controls the output of the debug messages.