Mostly to avoid polluting other logs and artifacts, and also to avoid
recompiling crosstests over and over.
--
v3: ci: Wrap complex commands in CI scripts.
ci: Build crosstests with -Wno-array-bounds.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/359
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52665
I'm unsure how to add tests for this given it requires an app to be installed via MSIX to get a package ID in Windows otherwise `IPackageStatics::get_Current()` returns `0x80073d54`.
--
v7: windows.applicationmodel: Implement IStorageItem::get_Path().
windows.applicationmodel/tests: Add IStorageItem::get_Path() tests.
windows.applicationmodel: Add IStorageItem stub interface.
windows.applicationmodel: Implement IPackage::get_InstalledLocation().
windows.applicationmodel: Implement IPackageStatics::get_Current().
windows.applicationmodel: Add IPackageStatics stub interface.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3548
Find only supports one Column to filter on.
The parser for this will be the same for both Find/Filter with the only different
is the Filter supports multiple columns.
In trying to keep this patch small, only WSTR/BSTR/Integer have been supported. (The Common cases).
--
v3: msado15: Implement _Recordset Find
https://gitlab.winehq.org/wine/wine/-/merge_requests/2498
On Fri Sep 22 06:50:36 2023 +0000, Aidan Khoury wrote:
> `RtlImageNtHeader` lacks proper image boundary checks for e_lfanew, so
> using it in this case is not safe.
this raises the questions does native ntdll.RtlImageHeader check for e_lfanew being within image boundary? if so, it builtin implementation has to be fixed (with test case please)
and if it doesn't you can still add the check on RtlImageHeader's returned value
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3870#note_46285
On Thu Sep 21 20:03:38 2023 +0000, Aidan Khoury wrote:
> No, but if you supply invalidly formed images to the mspatcha.dll APIs
> it will raise an exception with code 0xE0000001. I made this a separate
> function so I could mark it as `DECLSPEC_NORETURN`.
(my question was unclear: I meant does native throw this exception?)
what does native do if the exception is continued? (I doubt this helper can be DECLSPEC_NOTRETURN)
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3870#note_46284
> What about If I changed the commit message to winmm: MCI_MapMsgAtoW return error code directly instead of a boolean.
That's my point: it doesn't currently return a boolean, it returns a tri-state. One of those values tells the caller to skip calling `MCI_UnmapMsgAtoW()`. Your change gets rid of this.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3854#note_46283