[PATCH] d3d11/tests: Trace the name of the tests in single threaded mode.

[Henri Verbeet]

On Mon, 10 May 2021 at 16:14, Francois Gouget <fgouget at codeweavers.com> wrote:
> On Mon, 10 May 2021, Henri Verbeet wrote:
> > On Fri, 7 May 2021 at 19:39, Francois Gouget <fgouget at 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.
>
By convention:
    _queue_test_fl() -> queue_test_fl_()
    _queue_test() -> queue_test_()
    _queue_for_each_feature_level_in_range() ->
queue_for_each_feature_level_in_range_()
    _queue_for_each_feature_level() -> queue_for_each_feature_level_()
as well as preferring %u over %d in most cases.

> > 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/win2009_cw-gtx560-2009-32/d3d11:d3d11.html
> https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win2009_cw-rx460-2009-32/d3d11:d3d11.html
>
> No 'last test seen' message for those either:
> https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win2009_cw-rx460-2009-32/d3d10core:d3d10core.html
> https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win7_newtb-w7pro64-64/msxml3:domdoc.html
> https://test.winehq.org/data/99e47361a37a4bf16de131401a0c231f86214a43/win81_cw-gtx560-64/ntoskrnl.exe:ntoskrnl.html
>
> So it's not a problem with a specific test, nor with a specific Windows
> version. If someone knows what's going on...
>
Without having debugged it, my first guess would be that perhaps the
tls_data structure is getting corrupted somehow. Does that happen
consistently for that particular crash? Also, does that still happen
with WINETEST_NO_MT_D3D=1? Still, even if this particular
functionality happens to be broken in this case, for debug purposes
WINETEST_REPORT_SUCCESS=1 could serve much of the same purpose.