Just for anyone else's benefit, this ended up working for me:
$WINEDEBUG="trace+reg" wine /path/to/app.exe 2>&1 | tee winetrace.out
Doesn't work for some reason without using tee to capture the output.
Oh well, I'll do some digging in the file and see what I come up with.
Randall Walls
Molle Bestefich wrote:
Randall Walls wrote:
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.
Odd. Both work fine for me (using bash 3.0).
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.
Obviously you would need to add '>' or '1>' before 'winetrace',
assuming that winetrace is your desired log file.
And you would also need to make the redirection of stdout before the
stderr redirection, eg. "wine app.exe >winetrace 2>&1", not "wine
app.exe 2>&1 >winetrace".
What output from wine are you talking about? The occassional warnings?
Or is app.exe a console app?
Any other thoughts?
Try harder? :-)
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
