Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Windows versions 10v1507 and below classify a provider as an HWND
provider if it returns a value for UIA_NativeWindowHandle. By ignoring
this property, we get more consistent behavior in tests between all
Windows versions.
Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53813

Instead of silently leaking no longer used chunks.
Be more robust to OOM conditions.
Introducing pool_realloc().
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Create a dedicated heap for each module (as it was done for the
private home grown pools).
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

We can only get a successful status that way. This matches sock_recv().

Also combine the if (alerted) blocks. Unlike the previous commits, this cannot
be separated, as it causes warnings with some versions of gcc.

There is no need to release the async_fileio structure before calling set_async_direct_result().

We can only get a successful status that way. This matches sock_recv().

There is no need to release the async_fileio structure before calling set_async_direct_result().

We can only get a successful status that way. This avoids an uninitialized variable warning with gcc 12.2.

Wine-Bug: https://bugs.winehq.org//show_bug.cgi?id=53134

Fix a test failure when theming is off. A toolbar without TBSTYLE_FLAT will fill its checked button
background rectangle when theming is inactive, overwriting the checked pattern required for the test.

Some Windows version expect output to be aligned on 4 bytes.

Notes (from i386 and x86_64 tests):
- MSVC and Mingw/gcc don't layout the two variables (sdki, sdki_ex)
  the same way.
- MSVC aligns each variable on 4-byte boundary,
- MingW/GCC stores them in a 8-byte chunk, but starting from the
  end of the buffer: hence none of them is on a 4-byte boundary.

So, fixing the alignment of variables is not sufficient to
workaround the compilers' discrepancy on all source code.

I didn't find a generic way to align on 4 bytes structures of size
smaller than 4 bytes (apart from adding the DECLSPEC_ALIGN to
each of the offending structures, likely not that many though).
Ideas welcomed.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53684Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Needed to compile Tera Term.

The caller already analyses get_subtests() errors and provides
a detailed error message in the information section of the report
so the report(R_ERROR) pop up / stderr message is redundant.

Also add a full stop to match the other ERR() messages in
load_secondary_signatures().

Method decriptor's strings are internally stored in ANSI, and
potentially converted from Unicode using current code page.

Test was expecting loss in Unicode to ANSI conversion.
Adapt test to also support loss-less conversion (that's the case
when code page is UTF-8).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52873Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Fixes "Use of uninitialized value $Flaky" message in testbot reports.

Fixes "Use of uninitialized value $Flaky" message in testbot reports.

Fixes "Use of uninitialized value $Flaky" message in testbot reports.

This change is adding DWARF (CFI) unwind information to the
hand-written assembly of the `__wine_syscall_dispatcher` function.
This enables unwinding through the dispatcher from the Linux stack
into (and through) the Windows stack.

The general idea is that the `syscall_frame` struct contains the
content of the callee-save registers before the function call
(in particular the stack pointer and the return address). At any
point of the execution, we have a pointer into the `syscall_frame`
in $rcx, $rbp or $rsp.

For the CFI codes the general idea is that we are defining the
computations of the callee-save registers based on the
`syscall_frame` using DWARF’s `breg` instruction, rather than
relative to CFA.

This change adds a bunch of convenience macros, to (hopefully)
improve readability of the CFI instructions.

Note: Those change was used with great success for unwinding through
the dispatcher using a modified LLDB shown in the
“how-wine-works-101” (https://werat.dev/blog/how-wine-works-101/)
blog post as well as for in the Orbit profiler
(https://github.com/google/orbit), that has mixed-callstack
unwinding support.

Test: Inspect callstacks reported by the Orbit profiler while
running some Windows targets using the modified wine, as well as
verify debugging reports correct callstacks when stepping with our
modified LLDB through the dispatcher itself (so that we are able
to unwind through the dispatcher at any instruction).