https://bugs.winehq.org/show_bug.cgi?id=38227
Erich E. Hoover erich.e.hoover@wine-staging.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |erich.e.hoover@wine-staging | |.com
--- Comment #14 from Erich E. Hoover erich.e.hoover@wine-staging.com --- (In reply to rockman6112 from comment #13)
.... It is hard for me just send an excerption of the log file because it is multi-thread and it does not seem to me that there is an obvious way to find which lines belong to the problematic thread. So please let me know, how I can send those files to you for your work. Thanks ...
Your problem is outside my area of expertise, however, you can get Wine to report the thread of the log by adding "+tid" to WINEDEBUG. It's also important to note that when logging multithreaded applications it's useful to use appending (>>) instead of the normal output mechanism (>), otherwise it's possible for strange things to happen when multiple threads write to the log at the same time, for example: rm tmp.log; wine notepad 2>&1 >> tmp.log