I would please ask that you not question my loyalty to Google, or make
assumptions about my knowledge of the unix command line. For your
information, pipes, in the unix vernacular, refers to using one
command's output as input for a second command. What I am attempting to
do is output redirection. There is a very strict difference. :-P
I had already tried both suggestions that you made (with the exception
of adding the 'trace' class to the WINEDEBUG variable to limit the
output) and neither worked in the manner I expected. Setting WINEDEBUG
when I call wine to run the app does not appear to give me any trace
info at all, I have to export the variable prior to calling wine to get
the desired output. However, when I do this, I can't redirect it,
because appending 2>&1 winetrace to the end of wine app.exe would
redirect output from wine, and not what is coming from the trace.
Any other thoughts?
Randall Walls
Molle Bestefich wrote:
Randall Walls wrote:
Anyway to redirect the trace output to a file so I can grep through it?
There is a hugh amount of info that comes out of the trace.
Not a friend of Google, eh?
Seems a bit odd that you know grep but don't know how to use pipes. Hm..
Guessing that the trace output appears on stderr, do:
$ WINEDEBUG=+reg,+whatever wine app.exe 2> tracefile.log
to redirect stderr to a log file.
Or, to redirect both stdout and stderr to the same file:
$ WINEDEBUG=+reg,+whatever wine app.exe > tracefile.log 2>&1
Hm...
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
