On Mon, 10 May 2021, Henri Verbeet wrote:
On Fri, 7 May 2021 at 19:39, Francois Gouget fgouget@codeweavers.com wrote:
This allows figuring out which function the crash happens in when there is no backtrace. Just set WINETEST_NO_MT_D3D=1 WINETEST_DEBUG=2.
I'm not necessarily opposed to this (you do seem to have misplaced a number of *'s, as well as some other minor style issues though),
I can resubmit with the *s moved over but I don't know what the other issues are.
but don't the tests already print the last test seen before the exception on Windows? (And we're supposed to have backtraces everywhere else.)
Pretty often it does not as is obvious from many test results, and specifically not in this case. I don't know why though.
https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win200... https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win200...
No 'last test seen' message for those either: https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win200... https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win7_n... https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win81_...
So it's not a problem with a specific test, nor with a specific Windows version. If someone knows what's going on...