Use +threadname channel for thread names.
All threads resolved!
All threads resolved!
Currently, the two methods of setting thread names in Windows (SetThreadDescription() and the 0x406D1388 exception) log to different channels.
I think it would be useful for these to both log to the same +threadname channel. My thinking is that this would be similar to +debugstr, in that all messages are human-readable descriptions which would be useful for debugging crashes.
Merge request reports
Activity
- Resolved by Brendan Shanks
added 937 commits
-
6cbfc2d8...29dd8444 - 935 commits from branch
wine:master
- 62150e43 - ntdll: Use +threadname channel for thread rename exceptions.
- 5ef22dee - ntdll: Use +threadname channel for SetThreadDescription().
-
6cbfc2d8...29dd8444 - 935 commits from branch
added 55 commits
-
5ef22dee...fc128f66 - 53 commits from branch
wine:master
- 8a61b7c2 - ntdll: Use +threadname channel for thread rename exceptions.
- ee0fd30e - ntdll: Use +threadname channel for SetThreadDescription().
-
5ef22dee...fc128f66 - 53 commits from branch
Please register or sign in to reply