February 2023 - wine-gitlab

Re: [PATCH v5 0/8] MR1088: ntdll: Avoid calling pthread_exit on thread exit.
by Rémi Bernon (＠rbernon) 06 Feb '23

06 Feb '23

On Tue Oct 18 12:09:32 2022 +0000, **** wrote: > Marvin replied on the mailing list: > ``` > Hi, > It looks like your patch introduced the new failures shown below. > Please investigate and fix them before resubmitting your patch. > If they are not new, fixing them anyway would help a lot. Otherwise > please ask for the known failures list to be updated. > The tests also ran into some preexisting test failures. If you know how > to fix them that would be helpful. See the TestBot job for the details: > The full results can be found at: > https://testbot.winehq.org/JobDetails.pl?Key=125085 > Your paranoid android. > === debian11 (32 bit report) === > ddraw: > ddraw7.c:15663: Test failed: Expected unsynchronised map for flags 0x1000. > ddraw7.c:15663: Test failed: Expected unsynchronised map for flags 0x3000. > Report validation errors: > advapi32:security has no test summary line (early exit of the main process?) > advapi32:security has unaccounted for todo messages > kernel32:sync has no test summary line (early exit of the main process?) > === debian11 (build log) === > 01d0:err:winediag:d3d_device_create The application wants to create a > Direct3D device, but the current DirectDrawRenderer does not support this. > 01d0:err:winediag:d3d_device_create The application wants to create a > Direct3D device, but the current DirectDrawRenderer does not support this. > 01d0:err:winediag:d3d_device_create The application wants to create a > Direct3D device, but the current DirectDrawRenderer does not support this. > === debian11 (build log) === > Use of uninitialized value $Flaky in addition (+) at > /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24489. > Use of uninitialized value $Flaky in addition (+) at > /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24489. > Use of uninitialized value $Flaky in addition (+) at > /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24489. > ``` I believe these failures should be fixed now, the `kernel32:sync` failure was coming from a thread terminated before it started. This should work fine now. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1088#note_23056

1 0

Re: [PATCH v5 0/8] MR1088: ntdll: Avoid calling pthread_exit on thread exit.
by Rémi Bernon (＠rbernon) 06 Feb '23

06 Feb '23

I've implemented the frame unwind, using `_Unwind_ForcedUnwind` when available, in addition to skipping `pthread_exit`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1088#note_23054

1 0

[PATCH v2 0/6] MR2102: Add a partially implemented ir50_32 winmm video decoder, and a stub generic video decoder in winegstreamer.
by Shaun Ren (＠shaunren) 06 Feb '23

06 Feb '23

-- v2: ir50_32: Implement open and close. winegstreamer: Add video_decoder stub. https://gitlab.winehq.org/wine/wine/-/merge_requests/2102

4 10

[PATCH v5 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 06 Feb '23

06 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v5: ntdll: Do not send data to port 0. tests: Added to check if sending port 0 succeeds https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

3 3

[PATCH 0/1] MR2110: msi: Handle memory allocation failure in get_link_file (cppcheck).
by Alex Henrie (＠alexhenrie) 06 Feb '23

06 Feb '23

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

3 2

[PATCH v6 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 06 Feb '23

06 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v6: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

2 2

[PATCH v4 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 06 Feb '23

06 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v4: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

2 2

[PATCH v3 0/2] MR2100: Draft: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 06 Feb '23

06 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v3: ntdll: Do not send data to port 0. tests: Added to check if sending port 0 succeeds https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

2 2

[PATCH 0/2] MR2114: kernelbase: Fix performance of beatmap search in osu! Stable.
by Torge Matthies (＠tmatthies) 06 Feb '23

06 Feb '23

Commit 448e68ab5b937d168f5d091d8f65a7de534a9891 made searching for beatmaps in the in-game map list very slow, going from a few 100 ms to more than 10 seconds with my set of downloaded maps. The first commit in this MR fixes this problem, and the second commit potentially helps too. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2114

2 2

[PATCH v2 0/1] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 06 Feb '23

06 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v2: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

3 5

2025

2024

2023

2022

wine-gitlab February 2023