--
v2: user32/tests: Process messages while waiting in WindowFromPoint tests.
user32/tests: Check for window class registration failure normally.
user32/tests: Remove SetForegroundWindow success checks.
user32/tests: Remove unnecessary test skipping checks.
user32/tests: Fix indentation to silence a warning.
https://gitlab.winehq.org/wine/wine/-/merge_requests/169
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.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/89
This (in particular, the “explorer: …” commit) caused a regression for me. In an entirely headless configuration (configured with `--without-x`) on arm32 (probably happens on other architectures too, but that’s where it happened for me), when bootstrapping a new wineprefix (setting `WINEPREFIX` to a new, nonexistent directory, running `wine wineboot`), it can hang, printing errors like these:
```
0048:err:sync:RtlpWaitForCriticalSection section 7BC8A3F0 "../src/dlls/ntdll
/loader.c: loader_section" wait timed out in thread 0048, blocked by 0054, r
etrying (60 sec)
0048:err:sync:RtlpWaitForCriticalSection section 7BC8A3F0 "../src/dlls/ntdll
/loader.c: loader_section" wait timed out in thread 0048, blocked by 0054, r
etrying (60 sec)
```
Does this trigger some race condition when bootstrapping the environment?
(I can report it in bugzilla later, I presume that’s still preferred, I just happened to have better access to gitlab.)
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/162#note_1460