September 2025 - wine-gitlab

[PATCH v7 0/13] MR8995: Draft: ntdll/kernelbase: Add accurate node count feature to prevent memory access violations initializing multiple physical nodes as a single logical one on multi-node systems
by Danny Waser (＠wasertech) 19 Sep '25

19 Sep '25

A much cleaner result (written by hand) that we can reuse where needed later (_i.e._ `GetNumaProcessorNode` which also crashes with [a similar MAV](https://gist.github.com/wasertech/f894ce8d6250e72a01a861c0e4eb6064) on multi-node systems). Took me a while to understand where I should put everything, not even sure I got it right. Let me know. I thought I was going to need `FileNumaNodeInformation` but turns out it's not really needed. I can remove it if you want. This is what I see when I try to get a node count read: ```log 0024:fixme:ntdll:init_numa_info node affinity; using node 0. GetNumaHighestNodeNumber: 1 ``` I only see this fixme if I try to access `FILE_NUMA_NODE_INFORMATION`. I would really prefer such a behavior for our compatibility layer on any multi-node system. A big thanks to @besentv and @zfigura for their invaluable feedback on this. -- v7: kernel32/tests: fix parameter type in pGetNumaHighestNodeNumber and improve test messages https://gitlab.winehq.org/wine/wine/-/merge_requests/8995

2 13

[PATCH v2 0/3] MR9006: Several fixes & improvements when winedbg is started in auto mode.
by eric pouech (＠epo) 19 Sep '25

19 Sep '25

This series covers various fixes & improvements when a crash happens in a program which fires up winedbg in auto mode. Firstly, winedbg is a bit too strict for detecting the startup sequence (and fails to display the backtrace in these stricter cases). Third patch relaxes the startup conditions in that case. Secondly, if failing programs is a GUI, winedbg is launched in a new console (since GUI are now detached from console), but console is closed after winedbg terminates (which is after printing the crash details). So rather not useful :-( To work around this, conhost in its configuration dialog has tab 'Configuration' / 'End of program' / 'Close console' checkbox But which is not implemented. Second patch add supports for this in conhost. Lastly, conhost has the ability to store configuration per application. Hence, one can configure conhost with specific settings for winedbg. Interesting options are: - setting very high buffer zone so that conhost keeps track of all winedbg output, - unchecking the 'Close console' option. To set it for winedbg, - start it with './wine wineconsole winedbg' - use 'Properties' from the menu (right-click in conhost) to set the options for winedbg Since 68f3a8e699904bd308de0da4a1e1d2c9eb91ea96, conhost doesn't pick the registry entry for winedbg (if it exists) when started with './wine wineconsole winedbg'. Third patch solves that in a somehow hacky way, but couldn't find a better option that doesn't break https://bugs.winehq.org/show_bug.cgi?id=10941 -- v2: winedbg: No longer expect a startup sequence in auto mode. conhost: Support the close-on-exit configuration option. programs/wineconsole: Ensure conhost gets the expected title. https://gitlab.winehq.org/wine/wine/-/merge_requests/9006

3 6

[PATCH v6 0/13] MR8995: Draft: ntdll/kernelbase: Add accurate node count feature to prevent memory access violations initializing multiple physical nodes as a single logical one on multi-node systems
by Danny Waser (＠wasertech) 19 Sep '25

19 Sep '25

A much cleaner result (written by hand) that we can reuse where needed later (_i.e._ `GetNumaProcessorNode` which also crashes with [a similar MAV](https://gist.github.com/wasertech/f894ce8d6250e72a01a861c0e4eb6064) on multi-node systems). Took me a while to understand where I should put everything, not even sure I got it right. Let me know. I thought I was going to need `FileNumaNodeInformation` but turns out it's not really needed. I can remove it if you want. This is what I see when I try to get a node count read: ```log 0024:fixme:ntdll:init_numa_info node affinity; using node 0. GetNumaHighestNodeNumber: 1 ``` I only see this fixme if I try to access `FILE_NUMA_NODE_INFORMATION`. I would really prefer such a behavior for our compatibility layer on any multi-node system. A big thanks to @besentv and @zfigura for their invaluable feedback on this. -- v6: kernel32/tests: fix parameter type in pGetNumaHighestNodeNumber and improve test messages ntdll: improve return handling in init_numa_info and fix parameter checking https://gitlab.winehq.org/wine/wine/-/merge_requests/8995

2 12

[PATCH v3 0/4] MR8991: iphlpapi: Implement GetBestRoute2() and GetBestInterfaceEx().
by Paul Gofman (＠gofman) 19 Sep '25

19 Sep '25

-- v3: iphlpapi: Try to disambiguate addresses in GetBestRoute2() by probing system assigned ones. iphlpapi/tests: Add tests for best routes. iphlpapi: Reimplement GetBestInterfaceEx() on top of GetBestRoute2(). iphlpapi: Implement GetBestRoute2(). https://gitlab.winehq.org/wine/wine/-/merge_requests/8991

3 6

[PATCH 0/2] MR9013: propsys: Add PropVariantToFileTime() semi-stub.
by Nikolay Sivov (＠nsivov) 19 Sep '25

19 Sep '25

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9013

2 2

[PATCH v2 0/1] MR9007: wmic: Add a basic help option "/?".
by Louis Lenders (＠xe) 19 Sep '25

19 Sep '25

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45343 The installers from that bugreport use this (in Win7 mode) to check if wmic is present. (The installer still fails after this patch as findstr.exe lacks some support: "match_regexp character ranges (i.e. [abc], [^a-z]) are not supported") -- v2: wmic: Add a basic help option "/?". https://gitlab.winehq.org/wine/wine/-/merge_requests/9007

3 3

[PATCH 0/1] MR9012: opengl32: Propagate GL errors from wow64 wrappers.
by Jacek Caban (＠jacek) 19 Sep '25

19 Sep '25

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/9012

2 1

[PATCH 0/6] MR9011: Cmd engine rewrite (part XXXV)
by eric pouech (＠epo) 19 Sep '25

19 Sep '25

This is part XXXV of cmd engine rewrite. It : - fixes a regression introduced by previous serie, - fixed a couple of erroneous settings of some env variables (likely corner cases) But mostly, it's the start of implementing a pipe (between commands) as a pipe (IPC). Currently, cmd runs lhs of pipe, stores output into a file, then runs rhs with that file as input. However, this will expose a bunch of issues to be fixed before thinking implementing the IPC part. This serie covers the output part: - don't filter the stderr output in the paging (MORE) output, - send all stdout output to the paging (MORE), - use a line-buffered output for stdout, - adding some explicit flush before expecting input. It also fixes an issue triggered down the road. Next series (likely two) will cover the input part. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9011

2 6

[PATCH v6 0/1] MR8928: msxml3/tests: add test for IXMLDOMElement_removeAttributeNode.
by Reinhold Gschweicher (＠neroburner) 19 Sep '25

19 Sep '25

Implement test cases for `IXMLDOMElement_removeAttributeNode()` function. Cover the successful removal and failure codes for double removal and `NULL` pointer removal. The function is currently unimplemented in wine. This is the recommended first step according to the contribution documentation (do coverage MR first, then implementation MR). WineTestBot submission can be found here: https://testbot.winehq.org/JobDetails.pl?Key=159816 Once this one is merged I'll create the implementation MR. I tried to match the formatting. If I've missed something please tell me and I'll fix it. edit: remove mention of failing tests, update WineTestBot link, fixed by rebasing on 3cfbf9e3cd99dd01d3215c6952ae18ce88207d22 -- v6: msxml3/tests: add test for IXMLDOMElement_removeAttributeNode. https://gitlab.winehq.org/wine/wine/-/merge_requests/8928

3 3

[PATCH 0/1] MR8914: msxml: IXMLDOMNamedNodeMap::getNamedItem to handle global namespace.
by Alistair Leslie-Hughes (＠alesliehughes) 19 Sep '25

19 Sep '25

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/8914

3 3

2025

2024

2023

2022

wine-gitlab September 2025