May 2025 - Wine-Devel - list.winehq.org

Re: How do I determine which functions are unimplemented?

by Elizabeth Figura

On Tuesday, 6 May 2025 10:02:19 CDT Hin-Tak Leung wrote: > wine-dump can look at the import table. You can compare that with the export table from wine to see which routine is missing. > One non-wine solution is a piece of software called dependency walker. It looks at what a software requires at the api / dll level. That won't help. If an application calls a missing function that it links to directly, Wine should still name the function, in the terminal if nothing else. [BTW, please avoid top-posting on public lists.] > On Tuesday 6 May 2025 at 13:11:48 BST, zhengxianwei <baikaishiuc(a)gmail.com> wrote: > > When a function is commented out and the application calls it, the application crash silently . I dont know which function caused this. Is there any way to quickly determine which functions are unimplemented ? If the application is retrieving a function via GetProcAddress() and it's missing, you can try WINEDEBUG=warn+module. This will print a warning for every function that was not found. Be warned that it will include many false positives, though.

May 15, 2025

Re: How do I determine which functions are unimplemented?

by Hin-Tak Leung

wine-dump can look at the import table. You can compare that with the export table from wine to see which routine is missing. One non-wine solution is a piece of software called dependency walker. It looks at what a software requires at the api / dll level. On Tuesday 6 May 2025 at 13:11:48 BST, zhengxianwei <baikaishiuc(a)gmail.com> wrote: When a function is commented out and the application calls it, the application crash silently . I dont know which function caused this. Is there any way to quickly determine which functions are unimplemented ? eg: https://github.com/wine-mirror/wine/blob/226a7eeabbc13345e49da1ff8c018d6f06…

May 15, 2025

Re: How to use AddressSanitizer with Wine?

by Bernhard Übelacker

Am 28.04.25 um 06:44 schrieb Alex Henrie: > On Sat, Apr 26, 2025 at 4:36 PM Bernhard Übelacker > <bernhardu(a)mailbox.org> wrote: > >> For enabling ASan(PE) I collected some "notes to myself", which I hope >> are enough accurate to enable someone else to reproduce the results. > >> [6] https://gitlab.winehq.org/bernhardu/wine/-/blob/asan-pe_2025-04-05_wine-10.… > > Thank you for sharing! Goodness, it's a lot more complicated than I > had hoped. Notwithstanding the difficulty, following your instructions > closely I was able to build and run Wine with the llvm-mingw AUR > package.[1] My LLVM variables look like this: > > export LLVM_INST_PATH=/opt/llvm-mingw > export x86_64_LLVM_CLANG_RT_LIB=$(find $LLVM_INST_PATH -name > libclang_rt.asan_dynamic-x86_64.dll.a) > export i386_LLVM_CLANG_RT_LIB=$(find $LLVM_INST_PATH -name > libclang_rt.asan_dynamic-i386.dll.a) > > For my own sanity, I created scripts named configure64.sh, build64.sh, > configure32.sh, build32.sh, and run.sh for the various steps of the > instructions. I think it would be a lot easier to use your ASan branch > if the commands were already in scripts. > >> Unfortunately I have one patch with LLVM still in progress, >> therefore a self-built LLVM would be needed, to build wine. >> But this is just needed for HEAP_REALLOC_IN_PLACE_ONLY re-allocations, >> and running with "windows_hook_rtl_allocators=0" should not be affected by this, >> and that way building wine from the plain nightly llvm-mingw package should work. > > Could you note that in the README please? Upstream llvm-mingw combined > with windows_hook_rtl_allocators=1 resulted in the cryptic error > "wine: could not load kernel32.dll, status c0000135" when trying to > initialize and use the Wine prefix. > > I ran a few parts of the Wine test suite and I've submitted my first > patch based on the results.[2] Furthermore, since the instructions in > the wiki were outdated and nonfunctional, I've replaced them with a > link to your repository.[3] Thanks very much for all the work you put > into it! > > -Alex > > [1] https://aur.archlinux.org/packages/llvm-mingw > [2] https://gitlab.winehq.org/wine/wine/-/merge_requests/7925 > [3] https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#memory--address-c… Hello Alex, thanks for testing and fixing found issues. I missed also in the readme I am using currently a new-style-wow64 configure. Unfortunately I did not get around to put those parts into scripts. However, I rebased to current release and new test runs are in the asan_reports_x86(_64) subdirectories. https://gitlab.winehq.org/bernhardu/wine/-/tree/asan-pe_2025-04-26_wine-10.… Kind regards, Bernhard

May 15, 2025

Re: How to use AddressSanitizer with Wine?

by Bernhard Übelacker

Am 28.04.25 um 11:55 schrieb Yuxuan Shui: > Hi, > > I heard you were talking about ASan :) > > Just want to say that I happen to be working on ASan as well. Bernhard did > amazing work getting llvm's ASan runtime to work with Wine, however I am doing > a different approach. I want to be able to intrument the entirity of Wine, not > just PE. This has some challenges, created by e.g. the PE/Unix split, WoW64, > etc. I don't think any ASan runtimes can handle this yet, so I am working on > a special runtime for Wine. This is a lot of work, but on the flip side, this > should make running Wine under ASan much smoother, and rid us of the dependency > on compiler-rt. > > Ask me anything if this sounds interesting. Hopefully this idea doesn't sound > completely crazy to you ^^; > > Best, > Yuxuan Hello Yuxuan, this sounds interesting :-) I wondered if it would be possible to use PE and unix side with ASan enabled, and guessed this might need some changes in synchronising both to access a single Shadow memory, but never tried something into this direction. Kind regards, Bernhard

May 15, 2025

How do I determine which functions are unimplemented?

by zhengxianwei

When a function is commented out and the application calls it, the application crash silently . I dont know which function caused this. Is there any way to quickly determine which functions are unimplemented ? eg: https://github.com/wine-mirror/wine/blob/226a7eeabbc13345e49da1ff8c018d6f06…

May 15, 2025

Re: Why, in Wine, are some unimplemented APIs not marked as stubs but instead commented out?

by Zhiyi Zhang

If it's a stub, applications that link to it but don't actually call it works. If it's commented out, application might be able to handle its absence and fallback to other functions. Either way, if a application actually calls the function, it fails. So for such cases, you would need to implement the function. On 5/6/25 14:57, zhengxianwei wrote: > This results in a situation where, due to the missing API, the program > doesn't report an error but instead directly aborts; whereas if it > were marked as a stub, it would produce a clear error > > eg: > https://github.com/wine-mirror/wine/blob/226a7eeabbc13345e49da1ff8c018d6f06… > > Does this involve some of wine's development philosophy?

May 15, 2025

Re: Why, in Wine, are some unimplemented APIs not marked as stubs but instead commented out?

by zhengxianwei

Thank you—after your explanation, the choice between using a stub or commenting out an unimplemented API makes much more sense On Tue, May 6, 2025 at 5:03 PM Stefan Dösinger <stefandoesinger(a)gmail.com> wrote: > > > > Am 06.05.2025 um 10:13 schrieb Zhiyi Zhang <zzhang(a)codeweavers.com>: > > > > If it's a stub, applications that link to it but don't actually call it > works. If it's commented out, > > application might be able to handle its absence and fallback to other > functions. Either way, if > > a application actually calls the function, it fails. So for such cases, > you would need to implement the function. > > I'll try to phrase it a bit differently: Many applications dynamically > check if a function is available (via GetProcAddress). An @ stub will lead > such an application to believe the function is there, attempt to call it, > and crash. If the function is absent, it will fall back to alternatives and > have a decent chance of working. > > This mostly concerns functions that are only available on some Windows > versions. Usually they are introduced on newer Windows versions, but there > are functions that exist on Windows 9x but not on the Windows NT line. > >

May 15, 2025

Why, in Wine, are some unimplemented APIs not marked as stubs but instead commented out?

by zhengxianwei

This results in a situation where, due to the missing API, the program doesn't report an error but instead directly aborts; whereas if it were marked as a stub, it would produce a clear error eg: https://github.com/wine-mirror/wine/blob/226a7eeabbc13345e49da1ff8c018d6f06… Does this involve some of wine's development philosophy?

May 15, 2025

Re: Why, in Wine, are some unimplemented APIs not marked as stubs but instead commented out?

by Stefan Dösinger

> Am 06.05.2025 um 10:13 schrieb Zhiyi Zhang <zzhang(a)codeweavers.com>: > > If it's a stub, applications that link to it but don't actually call it works. If it's commented out, > application might be able to handle its absence and fallback to other functions. Either way, if > a application actually calls the function, it fails. So for such cases, you would need to implement the function. I'll try to phrase it a bit differently: Many applications dynamically check if a function is available (via GetProcAddress). An @ stub will lead such an application to believe the function is there, attempt to call it, and crash. If the function is absent, it will fall back to alternatives and have a decent chance of working. This mostly concerns functions that are only available on some Windows versions. Usually they are introduced on newer Windows versions, but there are functions that exist on Windows 9x but not on the Windows NT line.

May 15, 2025

Wine staging 10.7 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.7 (347 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * win32u: Fix return value of ScrollWindowEx for invisible windows. Removed (No longer required). * d3dx9_36-DDS (fixed upstream) Added: * None Updated: * vkd3d-latest * odbc32-fixes Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

May 15, 2025