March 2023 - Wine-bugs - list.winehq.org

[Bug 54739] New: oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54739 Bug ID: 54739 Summary: oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine: typelib.c:7057: Test failed: got 00000002 typelib.c:8195: Test failed: got wrong return code: 2, side: 0200 typelib.c:8231: Test failed: got: 80040155, side: 0200 typelib.c:8235: Test failed: got: 80040154, side: 0200 Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000000428dc1). [...] Backtrace: =>0 0x00000000428dc1 in oleaut32_test (+0x28dc1) (0x0000000050e538) 1 0x000000004460c8 in oleaut32_test (+0x460c8) (0x000000621080c0) 2 0x0000000050dbeb in oleaut32_test (+0x10dbeb) (0x00000000ab4415) 3 0x0000000050d447 in oleaut32_test (+0x10d447) (0000000000000000) 4 0x0000007b629409 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\kernel32\thread.c:61] in kernel32 (0000000000000000) 5 0x00000170061213 __wine_pop_frame(entry=000000000050D3E0, arg=00000000003F0000) [Z:\home\winetest\tools\testbot\var\wine\include\wine\exception.h:277] in ntdll (0000000000000000) 6 0x00000170061213 RtlUserThreadStart+0x83(entry=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:295] in ntdll (0000000000000000) 0x00000000428dc1 oleaut32_test+0x28dc1: mov (%rcx), %rax See https://test.winehq.org/data/patterns.html#oleaut32:typelib Where: 2 == ERROR_FILE_NOT_FOUND 0x80040154 == REGDB_E_CLASSNOTREG 0x80040155 == REGDB_E_IIDNOTREG -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 49787] New: Java fails to start with "Could not create the Java Virtual Machine" - "Could not reserve enough space for object heap"
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49787 Bug ID: 49787 Summary: Java fails to start with "Could not create the Java Virtual Machine" - "Could not reserve enough space for object heap" Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- You can download java from https://jdk.java.net/java-se-ri/7 (just unpack) To reproduce, just go into "bin" and run "wine java -Xmx1024M -version". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 49551] New: the installer tries to run Java 2 version 1.3.1 but failed
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49551 Bug ID: 49551 Summary: the installer tries to run Java 2 version 1.3.1 but failed Product: Wine Version: 1.8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pritishparihar95(a)gmail.com Distribution: --- Created attachment 67691 --> https://bugs.winehq.org/attachment.cgi?id=67691 Installanywhere windows for reference Installing Software Parashar Light Profession 7.0.1 After InstallAnywhere window no window comes up, I tried to find error code fron winedbg Error code: WineDbg starting on pid 001c 0x7b85f870: subl $8,%esp Invalid address (0x7b85f87a) for breakpoint 0, disabling it Process of pid=001c has terminated -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 53928] New: ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1
by WineHQ Bugzilla 26 Jun '23

26 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=53928 Bug ID: 53928 Summary: ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1 Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alandms123(a)gmail.com Distribution: --- Created attachment 73486 --> https://bugs.winehq.org/attachment.cgi?id=73486 wine.log OS: Arch Linux x86_64 Kernel: 6.0.8-arch1-1 nvidia drivers: 520.56.06-2 mesa: 22.2.3-1 WM: dwm cpu: i5-11400h dgpu: rtx 3050 laptop igpu: intel uhd graphics (tgl gt1) The only application I tried with was The Elder Scrolls Online. Basically with these versions of wine (6.16, 6.23, 7.0, 7.19, 7.20, 7.21) when using PRIME render offload (prime-run or setting the environment variables manually) a black screen will appear, killing the game processes or wine will not make X display anything again, the only way is switching to another tty and killing X from there. I did tried bisecting for a regression but couldn't go far, for example compiling 6.1-6.23 fails with something like conflicting types for ‘ldap_connect’. Also as I don't know which debug channel to provide the debug details the logs doesn't say much besides: 016c:err:system:ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1. The only versions which works, are the wine-tkg (https://github.com/Frogging-Family/wine-tkg-git/releases/tag/7.6.r12.g51472…) and ge-proton (https://github.com/GloriousEggroll/wine-ge-custom/releases/tag/GE-Proton7-33) If I can figure how to solve the conflicting types for ‘ldap_connect’, I'll try bisecting. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 37166] New: Multiple apps fail to detect removable (USB) disk devices (PNP device manager '{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}' device class GUID registry data missing)(TomTom, iTunes, Rufus)
by wine-bugs＠winehq.org 26 Jun '23

26 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37166 Bug ID: 37166 Summary: Multiple apps fail to detect removable (USB) disk devices (PNP device manager '{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}' device class GUID registry data missing)(TomTom, iTunes, Rufus) Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, continuation of bug 7711 and potentially others to avoid them being recycled over and over again. GUID '{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}' -> GUID_DEVINTERFACE_DISK MSDN: http://msdn.microsoft.com/en-us/library/windows/hardware/ff545824%28v=vs.85… Additionally the apps usually expect GUID '{F18A0E88-C30C-11D0-8815-00A0C906BED8}' class too -> GUID_DEVINTERFACE_USB_HUB http://msdn.microsoft.com/en-us/library/windows/hardware/ff545982%28v=vs.85…: Example trace log with 'Rufus': --- snip --- $ WINEDEBUG=+tid,+seh,+relay,+setupapi wine ./rufus-1.4.10.exe >>log.txt 2>&1 ... 0023:Call setupapi.SetupDiGetClassDevsA(004448fc,00000000,00000000,00000012) ret=0040ef60 0023:trace:setupapi:SetupDiGetClassDevsExW {f18a0e88-c30c-11d0-8815-00a0c906bed8} (null) (nil) 0x00000012 (nil) (null) (nil) 0023:warn:setupapi:SetupDiGetClassDevsExW unsupported flags 00000002 0023:trace:setupapi:SetupDiCreateDeviceInfoListExW {f18a0e88-c30c-11d0-8815-00a0c906bed8} (nil) (null) (nil) ... 0023:Call advapi32.RegOpenKeyExW(80000002,7e2e3bc0 L"System\\CurrentControlSet\\Control\\DeviceClasses",00000000,00020019,0077e944) ret=7e2bf207 0023:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=7e2bf207 0023:trace:setupapi:SETUPDI_EnumerateInterfaces 0x1e2408, {f18a0e88-c30c-11d0-8815-00a0c906bed8}, (null), 00000012 ... 0023:Ret setupapi.SetupDiGetClassDevsA() retval=001e2408 ret=0040ef60 ... 0023:Call setupapi.SetupDiEnumDeviceInfo(001e2408,00000000,0077ec91) ret=0040efd3 0023:trace:setupapi:SetupDiEnumDeviceInfo 0x1e2408 0 0x77ec91 0023:Ret setupapi.SetupDiEnumDeviceInfo() retval=00000000 ret=0040efd3 0023:Call setupapi.SetupDiDestroyDeviceInfoList(001e2408) ret=0040ef91 0023:trace:setupapi:SetupDiDestroyDeviceInfoList 0x1e2408 ... 0023:Ret setupapi.SetupDiDestroyDeviceInfoList() retval=00000001 ret=0040ef91 ... 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec24,004448b2 "USBSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec24 "USBSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec28,004448ba "UASPSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec28 "UASPSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec2c,004448c3 "VUSBSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec2c "VUSBSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec30,004448cc "ETRONSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec30 "ETRONSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.SetupDiGetClassDevsA(0044490c,00000000,00000000,00000012) ret=0040f350 0023:trace:setupapi:SetupDiGetClassDevsExW {53f56307-b6bf-11d0-94f2-00a0c91efb8b} (null) (nil) 0x00000012 (nil) (null) (nil) 0023:warn:setupapi:SetupDiGetClassDevsExW unsupported flags 00000002 0023:trace:setupapi:SetupDiCreateDeviceInfoListExW {53f56307-b6bf-11d0-94f2-00a0c91efb8b} (nil) (null) (nil) ... 0023:Call advapi32.RegOpenKeyExW(80000002,7e2e3bc0 L"System\\CurrentControlSet\\Control\\DeviceClasses",00000000,00020019,0077e944) ret=7e2bf207 0023:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=7e2bf207 0023:trace:setupapi:SETUPDI_EnumerateInterfaces 0x1e2408, {53f56307-b6bf-11d0-94f2-00a0c91efb8b}, (null), 00000012 ... 0023:Ret setupapi.SetupDiGetClassDevsA() retval=001e2408 ret=0040f350 0023:Call setupapi.SetupDiEnumDeviceInfo(001e2408,00000000,0077ec91) ret=0040f3c2 0023:trace:setupapi:SetupDiEnumDeviceInfo 0x1e2408 0 0x77ec91 0023:Ret setupapi.SetupDiEnumDeviceInfo() retval=00000000 ret=0040f3c2 0023:Call setupapi.SetupDiDestroyDeviceInfoList(001e2408) ret=004103c6 0023:trace:setupapi:SetupDiDestroyDeviceInfoList 0x1e2408 ... 0023:Ret setupapi.SetupDiDestroyDeviceInfoList() retval=00000001 ret=004103c6 ... 0023:Call KERNEL32.OutputDebugStringA(004640d4 "0 devices found\r\n") ret=004164fb ... 0023:Ret KERNEL32.OutputDebugStringA() retval=00000000 ret=004164fb ... --- snip --- $ sha1sum rufus-1.4.10.exe 031309c159429544a4e8bec0373d474c8e705c3e rufus-1.4.10.exe $ du -sh rufus-1.4.10.exe 1.4M rufus-1.4.10.exe $ wine --version wine-1.7.25 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 21

[Bug 41647] New: TFM Music Maker controls are not usable
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=41647 Bug ID: 41647 Summary: TFM Music Maker controls are not usable Product: Wine Version: 1.9.22 Hardware: x86 URL: http://sega4ever.power-heberg.com/Download/tfmmaker152 .rar OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: notasas(a)gmail.com Distribution: --- After starting the program, click "Instruments" tab and try to adjust any of the knobs. Nothing useful noticed in the terminal output. Just a guess it's an issue message handling, so selected user32 component. Tested to be broken on vanilla wine-1.9.22, wine-1.9.22 (Staging) and wine-1.6.2. Works correctly on real Windows 7 and 8.1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 5

[Bug 33326] New: Sound problem with Game Maker 8.0 games
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

http://bugs.winehq.org/show_bug.cgi?id=33326 Bug #: 33326 Summary: Sound problem with Game Maker 8.0 games Product: Wine Version: 1.5.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: georgiev_1994(a)abv.bg Classification: Unclassified When Im starting a game created from Game Maker 8.0 Po it's sound does not start. This is happening with every game Im trying to run. This is caused maybe because of the sound system of Game Maker built games. Here I will give a link just to one game which runs just perfect with Windows OS but not perfect at all with Wine. http://sandbox.yoyogames.com/games/205913/download -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 21

[Bug 40119] New: Irfanview 4.x: selection cursor is not correctly aligned
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=40119 Bug ID: 40119 Summary: Irfanview 4.x: selection cursor is not correctly aligned Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Ulf.Zibis(a)gmx.de Distribution: --- - select an area in an image - correct the selection by dragging the left selection border to another position --> the double-ended arrow cursor ofen is not correctly aligned with the selection border I guess this happens, when the image is zoomed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 9

[Bug 53682] New: wineboot shows "user_check_not_lock BUG: holding USER lock" on aarch64 since wine-7.14
by WineHQ Bugzilla 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=53682 Bug ID: 53682 Summary: wineboot shows "user_check_not_lock BUG: holding USER lock" on aarch64 since wine-7.14 Product: Wine Version: 7.14 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: PuetzKevinA(a)JohnDeere.com Distribution: --- I recently updated our builds to past wine-7.0, and began encountering a wineboot failure on aarch64 > 0040:err:system:user_check_not_lock BUG: holding USER lock(64) > s\system32\rundll32.exe: /home/yukondev/workspace/wine/dlls/win32u/sysparams.c:400: user_check_not_lock: Assertion `0' failed. > 0040:err:seh:call_function_handlers invalid frame 21f410 (0000000000022000-0000000000120000) > 0040:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. After some bisecting, I narrowed this down to being a regression between 7.13 and 7.14, and then further narrowed it to https://source.winehq.org/git/wine.git/commit/d50112b4b6e82782d3924a8dbd443… Somehow the call to KeUserModeCallback( NtUserLoadSysMenu,... ) at https://gitlab.winehq.org/wine/wine/-/blob/d50112b4b6e82782d3924a8dbd443f82… does not properly return. I think that commit is mostly a false lead though, the translation of syscall NtUserCreateWindowEx to a syscall just exposed a latent bug in KeUserModeCallback/__wine_syscall_dispatcher on aarch64, since having NtUserCreateWindowEx be a syscall means KeUserModeCallback can no longer use its "if we have no syscall frame, call the callback directly" simple path https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/unix/signal_ar… What seems to be actually at fault is that, inside of User32LoadSysMenu (the actual function invoked by KeUserModeCallback), is a call to NtUserCreateMenu - which is *also* a syscall. This call doesn't crash, and in fact all of User32LoadSysMenu runs to completion. But when it goes through __wine_syscall_dispatcher, the stack pointer is restored to be `$sp = arm64_thread_data()->syscall_frame` https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/unix/signal_ar… - i.e. it points to &callback_frame, back on the stack of KeUserModeCallback. And this is *not* the bottom of the stack; there's compiler-generated prologue/epilogue to restore various non-volatile registers. 0x0000ffffaa0247b4 <KeUserModeCallback+0>: sub sp, sp, #0x450 0x0000ffffaa0247b8 <KeUserModeCallback+4>: stp x29, x30, [sp] 0x0000ffffaa0247bc <KeUserModeCallback+8>: mov x29, sp 0x0000ffffaa0247c0 <KeUserModeCallback+12>: stp x19, x20, [sp, #16] 0x0000ffffaa0247c4 <KeUserModeCallback+16>: stp x21, x22, [sp, #32] 0x0000ffffaa0247c8 <KeUserModeCallback+20>: str w0, [sp, #56] 0x0000ffffaa0247cc <KeUserModeCallback+24>: str x1, [sp, #48] 0x0000ffffaa0247d0 <KeUserModeCallback+28>: str w2, [sp, #60] 0x0000ffffaa0247d4 <KeUserModeCallback+32>: mov x21, x3 0x0000ffffaa0247d8 <KeUserModeCallback+36>: mov x20, x4 0x0000ffffaa0247dc <KeUserModeCallback+40>: add x19, sp, #0x40 // x19=&callback_frame So any code that runs inside this syscall that uses the first 0x40 bytes of stack is trampling these variables in the frame of KeUserModeCallback. Eventually User32LoadSysMenu returns back into KiUserCallbackDispatcher, which passes it into NtCallbackReturn, which does a __wine_longjmp back into the KeUserModeCallback,and we exit from the __wine_setjmp for the second time (returning 0) and get to `return callback_frame.status` https://gitlab.winehq.org/wine/wine/-/blob/wine-7.17/dlls/ntdll/unix/signal…. But then the epilogue starts peeling off the stack => 0x0000ffffaa024864 <+176>: ldr w0, [sp, #1088] 0x0000ffffaa024868 <+180>: ldp x19, x20, [sp, #16] 0x0000ffffaa02486c <+184>: ldp x21, x22, [sp, #32] 0x0000ffffaa024870 <+188>: ldp x29, x30, [sp] 0x0000ffffaa024874 <+192>: add sp, sp, #0x450 0x0000ffffaa024878 <+196>: ret and the link register $x30 = (void *) 0xffffaa024984 <NtCallbackReturn+104>, rather than 0xffffa8f0ccdc <copy_sys_popup+44> as it was when it was pushed in the prologue. It's overwritten several times along the way, but I don't think any of these call sites are at fault; they are just writing to what they think is their own stack frame, unaware that __wine_syscall_dispatcher adjusted $sp to too-high a value and they are overwriting space that belongs to KeUserModeCallback. The specific places that overwrote this entry on the stack were #0 0x0000ffffa8f37a48 in NtUserCallOneParam (arg=0, code=2) at /home/yukondev/workspace/wine/dlls/win32u/sysparams.c:5357 #1 0x0000ffffaa022cf0 in __wine_syscall_dispatcher () from /opt/wine/bin/../lib/wine/aarch64-unix/ntdll.so which set it to 0xffffaa022cf0 <__wine_syscall_dispatcher+272> #0 insert_menu_item (ret_pos=0x21f538, flags=1024, id=4294967295, handle=0x10042) at /home/yukondev/workspace/wine/dlls/win32u/menu.c:438 #1 NtUserThunkedMenuItemInfo (handle=0x10042, pos=4294967295, flags=1024, method=1, info=0x11f528 <opengl_func_names+680>, str=<optimized out>) at /home/yukondev/workspace/wine/dlls/win32u/menu.c:1297 #2 0x0000ffffaa022cf0 in __wine_syscall_dispatcher () from /opt/wine/bin/../lib/wine/aarch64-unix/ntdll.so which set it to NULL and 0x0000ffffaa023a0c in NtCurrentTeb () at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:1449 1449 { (gdb) bt #0 0x0000ffffaa023a0c in NtCurrentTeb () at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:1449 #1 0x0000ffffaa02493c in ntdll_get_thread_data () at /home/yukondev/workspace/wine/dlls/ntdll/unix/unix_private.h:70 #2 arm64_thread_data () at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:163 #3 NtCallbackReturn (ret_ptr=0x0, ret_len=0, status=65602) at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:784 #4 0x0000ffffaa022cf0 in __wine_syscall_dispatcher () from /opt/wine/bin/../lib/wine/aarch64-unix/ntdll.so which set it to 0xffffaa02493c <NtCallbackReturn+32>, and then 0xffffaa024978 <NtCallbackReturn+92> , then 0xffffaa024984 <NtCallbackReturn+104> The same sort of thing happens in the x86_64 dispatcher, but there it turns out to be pretty harmless. The key difference is that the function prologue on x86_64 used `push` instructions, and did so prior to the `sub` where it allocated space for locals, so the things popped by the epilogue ended up above callback_frame, rather than below it, and so are not smashed. 0x00007fd17b6dc1d2 <+0>: push %rbp 0x00007fd17b6dc1d3 <+1>: mov %rsp,%rbp 0x00007fd17b6dc1d6 <+4>: push %r14 0x00007fd17b6dc1d8 <+6>: push %r13 0x00007fd17b6dc1da <+8>: push %r12 0x00007fd17b6dc1dc <+10>: push %rdi 0x00007fd17b6dc1dd <+11>: push %rsi 0x00007fd17b6dc1de <+12>: push %rbx 0x00007fd17b6dc1df <+13>: sub $0xa0,%rsp 0x00007fd17b6dc1e6 <+20>: and $0xffffffffffffffc0,%rsp 0x00007fd17b6dc1ea <+24>: sub $0x560,%rsp There is still a 32-byte gap between the $rsp of KeUserModeCallback and &current_frame that is briefly at risk, but 1. This seems to be the register parameter area of the Windows x64 ABI, which is actually volatile space that belongs to the callee even though it's allocated by the caller, so the compiler is not expecting it to survive across function calls (in this case __wine_syscall_dispatcher_return). https://docs.microsoft.com/en-us/cpp/build/stack-usage?view=msvc-170 discusses how this "contains at least 4 entries", i.e. 32 bytes: https://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64 2. It doesn't actually get smashed, because __wine_syscall_dispatcher subtracts 0x20 from the restored $rsp before actually making the syscall (https://gitlab.winehq.org/wine/wine/-/blob/d50112b4b6e82782d3924a8dbd443f82…) Which is presumably since the SysV ABI does *not* make any such reservation, and so __wine_syscall_dispatcher needs to do so to be following the ms_abi. So together, these mean that on x86_64, it would be OK if __wine_syscall_dispatcher used these 32 bytes between the correct $rsp of KeUserModeCallback and frame->syscall_table (though it doesn't seem to). And the eventual callee gets a $rsp that does *not* overlap with KeUserModeCallback (even though it would be legal for it to do so). I don't know that we have any actual guarantee that callback_frame will be at the bottom, but in practice it seems to be. But on aarch64, there's important stuff below callback_frame, so this doesn't work out. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 54442] New: experimental wow64 mode: doesn't show some graphical windows
by WineHQ Bugzilla 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54442 Bug ID: 54442 Summary: experimental wow64 mode: doesn't show some graphical windows Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru Distribution: --- Created attachment 73990 --> https://bugs.winehq.org/attachment.cgi?id=73990 SteamSetup.png When I'm building wine with new experimental wow64 mode, it is unable to properly show or render application windows for some applications. I've tried it both on clean prefix and on existing prefix. I've tried Steam setup and Battle.net setup, both failed. With Battle.net setup I see no window, with Steam setup I see black window with some artifacts. When using multilib wine built old way, everything works as usual. Happens both with wine 8.0 and 8.1. OS: Gentoo Linux amd64 (64bit) Graphics: X11 Videocard information: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K1000M/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.161.03 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile Wine build options: ./configure --with-mingw --enable-archs='i386,x86_64' --prefix=/tmp/wineinstall Default wine output: $ WINEPREFIX=/tmp/wineprefix/prefix1 /tmp/wineinstall/bin/wine /tmp/SteamSetup.exe 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0090:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 010c:err:environ:init_peb starting L"Z:\\tmp\\SteamSetup.exe" in experimental wow64 mode 010c:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 010c:fixme:imm:ImeSetActiveContext (00020046, 1): stub 010c:fixme:imm:ImmReleaseContext (00010052, 00020046): stub 0090:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub 0090:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 9