Hello,
Trying to understand why Fallout New Vegas doesn't start on my machine, I wanted to start wine with WINEDEBUG=+all (overkill but...)
However, trying in the shell
$ WINEDEBUG=+all wine FalloutNV.exe out.log 2>&1
I get only a few starting lines, and most of the other lines are not in out.log. I guess this is because multiple threads are started, each with its own stdout and stderr, so that only the out and err of the original are thread are in out.log.
Is there a way to tell wine itself to redirect all its output to a file? I looked in the FAQ but haven't seen (or haven't found) anything relevant, and no more luck on the net (I found plenty of pages on redirecting output in the shell but nothing different than &>).
Thanks!
Redirecting wine messages to a log file
- DarkShadow44
- Level 8
- Posts: 1207
- Joined: Tue Nov 22, 2016 5:39 pm
Re: Redirecting wine messages to a log file
Try "WINEDEBUG=+all wine FalloutNV.exe &> out.log" if you use a shell that supports it, or "WINEDEBUG=+all wine FalloutNV.exe >out.log 2>&1" if you don't.
Re: Redirecting wine messages to a log file
Thanks, it seems to work your way! :^)