- support 8 byte targets
- default to CPU pointer size if size isn't present nor supported.
- detect unaligned requests
Signed-off-by: Eric Pouech <eric.pouech@codeweavers.com>
This also correctly initialize some lvalue.
Context of the bug has changed, but the underlying issue remained the same.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=39495
Signed-off-by: Eric Pouech <eric.pouech@codeweavers.com>
Currently, dbghelp returns the source file either:
- in DOS format when native module option isn't enabled
- as stored in debug info format otherwise
This used to work for PE modules inside ELF shared libraries but is broken
since evolution to REAL modules. This generates several issues:
- winedbg does not always set the native module option when calling dbghelp
for source file related functions, leading to heterogenous output to user
- some dbghelp function rely on matching source paths, hence leading to
errors in winedbg when mixing the two formats for the same source file.
Introduce a new Wine only dbghelp option to return the source paths as they
are stored inside debug information format, and activate it unconditionaly
inside winedbg.
This fixes some failure cases of command 'break <NN>' in winedbg.
Signed-off-by: Eric Pouech <epouech@codeweavers.com>
Fixes an issue where a window's image would be stretched as it was moved
further offscreen.
The offscreen part of a window also did not display correctly in Exposé.
Note that this adds a todo_wine to test_get_blob_part2(). It looks
like native d3dcompiler only adds padding between sections, while
vkd3d-shader always adds padding to the end of sections. I've sent a
vkd3d-shader patch to fix that, but the extra padding at the end of
the DXBC blob doesn't seem terribly concerning.
The app I'm considering opens a video_processor on its own, with
a NV12 format on input and a ARGB32 format on output.
Tested on Windows: the samples are flipped vertically. While Wine
keeps them untouched.
So added a videoflip in the video processor to be activated when needed.
Signed-off-by: Eric Pouech <epouech@codeweavers.com>
WM_CHAR interprets the character codes using a code page tied to the
keyboard layout, not CP_ACP.
Also skip the test if WideCharToMultiByte() used the default character
since that breaks the round-trip.
Trace the code page when skipping the tests.
Wine-Bug: https://bugs.winehq.org//show_bug.cgi?id=54424
