- Wine-gitlab - list.winehq.org

[PATCH 0/2] MR9711: msado15: Remove left over free in get_accessor (ASan).
by Bernhard Übelacker 08 Dec '25

08 Dec '25

The first patch removes an unconditional `free( key )`, which holds here a pointer to the stack variable `tmp`. I assume this is a left over, because the next line outside the block is again a `free( key )`, this time with condition. The second patch adds a return in case the `malloc` of `elem` failed. Are both of my assumptions right here? Followup to f2ea57b7b7. CC: @piotr [ASan report in gitlab](https://gitlab.winehq.org/bernhardu/wine/-/jobs/215621#L6107) <details> <summary>ASan details</summary> ``` (lldb) bt * thread #1, stop reason = breakpoint 1.4 * frame #0: 0x79e8b843 libclang_rt.asan_dynamic-i386.dll`ReportError at asan_report.cpp:227:29 [inlined] frame #1: 0x79e8b843 libclang_rt.asan_dynamic-i386.dll`::ReportFreeNotMalloced() at asan_report.cpp:269:13 frame #2: 0x79e68da4 libclang_rt.asan_dynamic-i386.dll`::Deallocate() at asan_allocator.cpp:0 frame #3: 0x79e66cb8 libclang_rt.asan_dynamic-i386.dll`__ZN6__asan9asan_freeEPvPN11__sanitizer18BufferedStackTraceE at asan_allocator.cpp:1017:12 frame #4: 0x79e8520c libclang_rt.asan_dynamic-i386.dll`::free() at asan_malloc_win.cpp:72:10 frame #5: 0x6e9ab979 msado15.dll`get_accessor(recordset=0x03403970, fields=0x0059f8f0, hacc=0x0059f940) at recordset.c:2280 frame #6: 0x6e9a11e9 msado15.dll`_recordset_AddNew(a)36(iface=<unavailable>, field_list=<unavailable>, values=<unavailable>) at recordset.c:2326 frame #7: 0x0041107a msado15_test.exe`_Recordset_AddNew(This=<unavailable>, field_list=<unavailable>, values=<unavailable>) at msado15_backcompat.h:5779 frame #8: 0x00405c01 msado15_test.exe`test_ADORecordsetConstruction(exact_scroll=<unavailable>) at msado15.c:2061 frame #9: 0x00401038 msado15_test.exe`func_msado15 at msado15.c:3221 frame #10: 0x0041a662 msado15_test.exe`run_test(name="msado15") at test.h:780 frame #11: 0x0041a17c msado15_test.exe`main(argc=<unavailable>, argv=<unavailable>) at test.h:0 frame #12: 0x0041be56 msado15_test.exe`mainCRTStartup at crt_main.c:62 frame #13: 0x7bd33690 kernel32.dll`BaseThreadInitThunk + 16 frame #14: 0x7be667ab ntdll.dll`_call_thread_func_wrapper + 23 frame #15: 0x7be6711b ntdll.dll`call_thread_func(entry=(msado15_test.exe`mainCRTStartup at crt_main.c:45), arg=0x7ffd1000) at signal_i386.c:503 (lldb) frame select 5 frame #5: 0x6e9ab979 msado15.dll`get_accessor(recordset=0x03403970, fields=0x0059f8f0, hacc=0x0059f940) at recordset.c:2280 2277 memcpy( elem->key.data, key->data, key->len * sizeof(key->data[0]) ); 2278 rb_put( &recordset->hacc_cache, key, &elem->entry ); 2279 } -> 2280 free( key ); 2281 } 2282 if ((BYTE *)key != tmp) free( key ); 2283 (lldb) print key (hacc_cache_key *) 0x0059f6c0 (lldb) print (char*)tmp (char *) 0x0059f6c0 "" (lldb) ================================================================= ==msado15_test.exe==1092==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x0059f6c0 in thread T0 #0 0x79e851bb in free /home/runner/work/llvm-mingw/llvm-mingw/llvm-project/compiler-rt\lib/asan/asan_malloc_win.cpp:71:3 #1 0x6e9ab978 in get_accessor .../wine/dlls/msado15/recordset.c:2280 #2 0x6e9a11e8 in recordset_AddNew .../wine/dlls/msado15/recordset.c:2326 #3 0x00411079 in _Recordset_AddNew .../obj\include\msado15_backcompat.h:5779 #4 0x00405c00 in test_ADORecordsetConstruction .../wine/dlls/msado15/tests/msado15.c:2061 #5 0x00401037 in func_msado15 .../wine/dlls/msado15/tests/msado15.c:3221 #6 0x0041a661 in run_test .../wine/include/wine/test.h:780 #7 0x0041a17b in main .../wine/include/wine/test.h #8 0x0041be55 in mainCRTStartup .../wine/dlls/msvcrt/crt_main.c:62 #9 0x7bd3368f in BaseThreadInitThunk (C:\windows\system32\kernel32.dll+0x7b82368f) #10 0x7be667aa in call_thread_func_wrapper (C:\windows\system32\ntdll.dll+0x7bc467aa) #11 0x7be6711a in call_thread_func .../wine/dlls/ntdll/signal_i386.c:503 Address 0x0059f6c0 is located in stack of thread T0 at offset 32 in frame #0 0x6e9aac2f in get_accessor .../wine/dlls/msado15/recordset.c:2179 This frame has 2 object(s): [16, 20) 'refcount' (line 2182) [32, 288) 'tmp' (line 2183) <== Memory access at offset 32 is inside this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp, SEH and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: bad-free .../wine/dlls/msado15/recordset.c:2280 in get_accessor ``` </details> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9711

2 3

[PATCH 0/1] MR9720: msado15: Ignore IRowset:GetProperties return value in rsconstruction_put_Rowset (Coverity).
by Piotr Caban (＠piotr) 08 Dec '25

08 Dec '25

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

2 1

Re: [PATCH v3 0/1] MR8701: devenum: Add DevicePath field for a video input device.
by Haoyang Chen (＠chenhaoyang) 08 Dec '25

08 Dec '25

On Mon Dec 8 01:49:57 2025 +0000, Bernhard Übelacker wrote: > I submitted MR !9707 which copies above skip when no device is found > from qcap to devenum, hope that is ok. Hi Bernhard Übelacker. Thank you very much for your feedback and the suggested fix! This test requires a webcam to function properly. I have reviewed your code [!9707](https://gitlab.winehq.org/wine/wine/-/merge_requests/9707) and indeed need to skip it. I really appreciate you taking the time to look into this and provide such a clear solution. Thanks again! -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8701#note_125121

1 0

[PATCH v2 0/3] MR9646: mf/tests: Scrubbing tests
by Brendan McGrath (＠redmcg) 08 Dec '25

08 Dec '25

This MR adds tests for how scrubbing and rate changes work within the Media Session. -- v2: mf/tests: Check that Rate change in PLAY state is ignored. mf/tests: Test that there is no pre-roll during scrubbing. mf/tests: Modify test_seek_clock_sink to be ref counted. https://gitlab.winehq.org/wine/wine/-/merge_requests/9646

2 6

[PATCH 0/6] MR9718: amstream, quartz, ir50_32: Plumb the sample rect.
by Elizabeth Figura (＠zfigura) 07 Dec '25

07 Dec '25

Earth 2150 uses this. This fixes a regression from 2f180106471a41fa3d95f21919b87b94d8e13e63. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9718

2 6

[PATCH v2 0/3] MR9717: winegstreamer: Handle dynamic format change.
by Elizabeth Figura (＠zfigura) 07 Dec '25

07 Dec '25

-- v2: winegstreamer: Handle dynamic format change. https://gitlab.winehq.org/wine/wine/-/merge_requests/9717

2 4

[PATCH 0/3] MR9717: winegstreamer: Handle dynamic format change.
by Elizabeth Figura (＠zfigura) 07 Dec '25

07 Dec '25

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

2 3

[PATCH v8 0/11] MR9628: user32: Implement pointer input APIs for multi-touch support
by Hecheng Yu (＠kde-yyds) 07 Dec '25

07 Dec '25

This patch implements core pointer input APIs required by modern applications with touchscreen support, particularly Chromium and Qt-based applications. Implemented APIs: - GetPointerType: Query pointer input type (touch, pen, mouse) - GetPointerTouchInfo: Retrieve detailed touch pointer information - GetPointerFrameTouchInfo: Get all active touch pointers in current frame Added stubs: - SkipPointerFrameMessages: Used by applications to skip pointer frame processing like Qt - GetPointerFrameTouchInfoHistory: Historical touch frame data (not yet implemented) - GetPointerPenInfoHistory: Historical pen data (not yet implemented) System metrics changes: - SM_DIGITIZER: Reports touch capabilities (NID_INTEGRATED_TOUCH | NID_MULTI_INPUT | NID_READY) - SM_MAXIMUMTOUCHES: Returns maximum simultaneous touch points (10) Limitations: - We explictly set pointer type to PT_TOUCH when storing pointer info to queue, so GetPointerType will always return PT_TOUCH - GetPointerFrameTouchInfo returns 0 pointers after finger lift, while Windows returns 1 pointer with UP flags. And SkipPointerFrameMessages is currently a stub returning TRUE. Qt's pointer message processing uses both of them, but it's just working well Application requirements: - Chromium: Requires GetPointerType and GetPointerTouchInfo for touch input - Qt applications: Need GetPointerFrameTouchInfo and proper system metrics for multi-touch support - Qt5: Additionally checks for presence of all pointer APIs at runtime, requiring stubs to enable pointer messages processing -- v8: user32: Implement GetPointerFrameTouchInfo win32u: Implement NtUserGetPointerFrameTouchInfo user32: Implement GetPointerTouchInfo win32u: Implement NtUserGetPointerTouchInfo user32: Implement GetPointerType win32u: Implement NtUserGetPointerType win32u: Add pointer information cache and storage user32: Stub GetPointerPenInfoHistory user32: Stub GetPointerFrameTouchInfoHistory user32: Stub SkipPointerFrameMessages win32u: Add SM_DIGITIZER and SM_MAXIMUMTOUCHES system metrics https://gitlab.winehq.org/wine/wine/-/merge_requests/9628

2 11

[PATCH v7 0/11] MR9628: user32: Implement pointer input APIs for multi-touch support
by Hecheng Yu (＠kde-yyds) 06 Dec '25

06 Dec '25

This patch implements core pointer input APIs required by modern applications with touchscreen support, particularly Chromium and Qt-based applications. Implemented APIs: - GetPointerType: Query pointer input type (touch, pen, mouse) - GetPointerTouchInfo: Retrieve detailed touch pointer information - GetPointerFrameTouchInfo: Get all active touch pointers in current frame Added stubs: - SkipPointerFrameMessages: Used by applications to skip pointer frame processing like Qt - GetPointerFrameTouchInfoHistory: Historical touch frame data (not yet implemented) - GetPointerPenInfoHistory: Historical pen data (not yet implemented) System metrics changes: - SM_DIGITIZER: Reports touch capabilities (NID_INTEGRATED_TOUCH | NID_MULTI_INPUT | NID_READY) - SM_MAXIMUMTOUCHES: Returns maximum simultaneous touch points (10) Limitations: - We explictly set pointer type to PT_TOUCH when storing pointer info to queue, so GetPointerType will always return PT_TOUCH - GetPointerFrameTouchInfo returns 0 pointers after finger lift, while Windows returns 1 pointer with UP flags. And SkipPointerFrameMessages is currently a stub returning TRUE. Qt's pointer message processing uses both of them, but it's just working well Application requirements: - Chromium: Requires GetPointerType and GetPointerTouchInfo for touch input - Qt applications: Need GetPointerFrameTouchInfo and proper system metrics for multi-touch support - Qt5: Additionally checks for presence of all pointer APIs at runtime, requiring stubs to enable pointer messages processing -- v7: user32: Implement GetPointerFrameTouchInfo win32u: Implement NtUserGetPointerFrameTouchInfo user32: Implement GetPointerTouchInfo win32u: Implement NtUserGetPointerTouchInfo user32: Implement GetPointerType win32u: Implement NtUserGetPointerType win32u: Add pointer information cache and storage user32: Stub GetPointerPenInfoHistory user32: Stub GetPointerFrameTouchInfoHistory user32: Stub SkipPointerFrameMessages win32u: Add SM_DIGITIZER and SM_MAXIMUMTOUCHES system metrics https://gitlab.winehq.org/wine/wine/-/merge_requests/9628

2 11

Re: [PATCH v6 0/11] MR9628: user32: Implement pointer input APIs for multi-touch support
by Hecheng Yu (＠kde-yyds) 06 Dec '25

06 Dec '25

On Mon Dec 1 14:57:26 2025 +0000, Hecheng Yu wrote: > For new APIs maybe yes Now splited. Tests will also appear later. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9628#note_125084

1 0