[Bug 56365] New: ntdll-Syscall_Emulation patchset causing xdelta3 process to crash/fail
https://bugs.winehq.org/show_bug.cgi?id=56365 Bug ID: 56365 Summary: ntdll-Syscall_Emulation patchset causing xdelta3 process to crash/fail Product: Wine-staging Version: 9.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madbyte(a)tuta.io CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 76104 --> https://bugs.winehq.org/attachment.cgi?id=76104 log winedebug_seh wine-staging-9.2 Me and a bunch of other users encounter an issue while using a delta patcher used to downpatch a specific game to an earlier game version. The delta patcher utilizes xdelta3. I found that the xdelta3 process seemingly fails at a random file while patching the game data. I started building wine-staging from source myself and after some testing and excluding seemingly relevant patchsets I found that excluding the patch 'ntdll-Syscall_Emulation' will result in the patcher finishing it's job without issues. The issue using vanilla wine-staging builds seemed to not be consistent between distros as well: Tests always failed on e.g Pop!_Os, CachyOS, EndeavourOS, Garuda, but on e.g Fedora 39, Mint 21.3, Manjaro, Ubuntu 23.10 the patching worked every time, even with the ntdll-Syscall_Emulation patchset enabled. I guessed it might be because of some kernel option/feature enabled/disabled by default on some distros but didn't want to built kernels from source myself to test this. In case it helps, here is the patcher src snippet from where the xdelta3 process is invoked: https://dev.sp-tarkov.com/waffle.lord/Patcher/src/branch/main/Patcher/Patche... (the error log of the patcher itself shows the message seen on line 113, "something went wrong during the xdelta3 process") I've attached a log showing a failed attempt with wine-staging-9.2 including said patchset. imho the relevant part starts at line 14726 in the file: 0748:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005. 0748:trace:seh:install_bpf Seccomp filters already installed. 0748:fixme:ver:GetCurrentPackageId (000000000063FEB0 0000000000000000): stub 02c4:trace:seh:dispatch_exception code=e0434352 flags=1 addr=00006FFFFFC135A7 ip=6fffffc135a7 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56365 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56365 --- Comment #1 from Lars Loe <madbyte(a)tuta.io> --- A couple more clarifications: - The log was generated using vanilla wine-staging-9.2 on Pop!_Os. - wine-stable 9.0 up to 9.2 had no issues running this delta patcher. - I've excluded only this one patchset from my wine-staging build, resulting in the patcher working consistently. I'll gladly support if there's any more information needed. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56365 Lars Loe <madbyte(a)tuta.io> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madbyte(a)tuta.io --- Comment #2 from Lars Loe <madbyte(a)tuta.io> --- I might have miss interpreted the exception in the log.. I believe the relevant part has to be this event: 02c4:trace:seh:dispatch_exception code=e0434352 flags=1 addr=00006FFFFFC135A7 ip=6fffffc135a7 02c4:trace:seh:dispatch_exception info[0]=ffffffff80004005 02c4:trace:seh:dispatch_exception info[1]=0000000000000000 02c4:trace:seh:dispatch_exception info[2]=0000000000000000 02c4:trace:seh:dispatch_exception info[3]=0000000000000000 02c4:trace:seh:dispatch_exception info[4]=0000000140000000 02c4:warn:seh:dispatch_exception unknown exception (code=e0434352) raised 02c4:trace:seh:dispatch_exception rax=0000000024d0ec70 rbx=0000000024d0ed58 rcx=0000000024d0ec30 rdx=0000000000000000 02c4:trace:seh:dispatch_exception rsi=0000000000000005 rdi=0000000000000001 rbp=0000000024d0f170 rsp=0000000024d0ec10 02c4:trace:seh:dispatch_exception r8=0000000140000000 r9=0000000024d0ed78 r10=000000000308ad30 r11=0000000024d0eb90 02c4:trace:seh:dispatch_exception r12=0000000000000000 r13=0000000000000000 r14=00000000e0434352 r15=000000000000054f 02c4:trace:seh:call_vectored_handlers calling handler at 000000014005D380 code=e0434352 flags=1 02c4:trace:seh:call_vectored_handlers handler at 000000014005D380 returned 0 02c4:trace:seh:call_handler calling handler 00000001405A26E8 (rec=0000000024D0EC30, frame=0000000024D0ECE0 context=0000000024D0E170, dispatch=0000000024D0E040) 02c4:trace:seh:call_handler handler at 00000001405A26E8 returned 1 02c4:trace:seh:call_handler calling handler 00000001405A7FB8 (rec=0000000024D0EC30, frame=0000000024D0EDB0 context=0000000024D0E170, dispatch=0000000024D0E040) 02c4:trace:seh:call_handler handler at 00000001405A7FB8 returned 1 02c4:trace:seh:call_handler calling handler 00000000E1790000 (rec=0000000024D0EC30, frame=0000000024D0F110 context=0000000024D0E170, dispatch=0000000024D0E040) 02c4:trace:seh:call_handler handler at 00000000E1790000 returned 1 02c4:trace:seh:call_handler calling handler 00000000E1790000 (rec=0000000024D0EC30, frame=0000000024D0F350 context=0000000024D0E170, dispatch=0000000024D0E040) 02a4:err:esync:__esync_wait_objects Polling on fd 20 returned 0x20. -- 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.
participants (1)
-
WineHQ Bugzilla