[Bug 43656] New: World of Warcraft crash on startup with stack overflow
https://bugs.winehq.org/show_bug.cgi?id=43656 Bug ID: 43656 Summary: World of Warcraft crash on startup with stack overflow Product: Wine Version: 2.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 59089 --> https://bugs.winehq.org/attachment.cgi?id=59089 wine 2.16 default console log A few days ago it did start fine with wine 2.15. Today I upgraded to wine 2.16 and there was also a game update in the Blizzard App. Now I cannot start the game anymore, even with wine 2.15 and 2.14 that used to work. There is no error window, the program just close when starting. There is an err:seh stack overflow at the end of the log. -- 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=43656 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64 Distribution|--- |Debian -- 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=43656 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=43656 --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Disabling CSMT does not fix the issue. Issue is present in either winXP and win7 mode. Issue is NOT present with wine-staging 2.15. -- 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=43656 Gero <gero45(a)mr-gero.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gero45(a)mr-gero.de --- Comment #2 from Gero <gero45(a)mr-gero.de> --- I also have this problem. Issue is present with Wine-Staging 2.15. -- 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=43656 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de --- Comment #3 from Ker noa <blue-t(a)web.de> --- The problem is that last weeks 7.3 update added a whole new layer of anti-cheat protection in the game. So it might be related to that and https://bugs.winehq.org/show_bug.cgi?id=40479 -- 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=43656 Kevin Brott <winebugz(a)kbrm.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugz(a)kbrm.net --- Comment #4 from Kevin Brott <winebugz(a)kbrm.net> --- Debian 9 / Wine 2.15 staging / 64-bit Win7 container Blizzard App 1.8.6.9262 / WoW 7.3.0.24974 Post Wow 7.3.0 patch, launch would abort with "Cannot initialize Application". Configured Blizzard App options to launch WoW in 32-bit mode (D3D9), & now game starts and plays (impaired FPS, but it works and is playable on my older hardware). Occasional initial startup crash with error #135 - but a second game start typically works. Spent most of today leveling my fire mage, so confirmed it does still work on 2.15 staging. -- 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=43656 --- Comment #5 from Kevin Brott <winebugz(a)kbrm.net> --- Upgraded to 2.16.0~stretch - no change in functionality/behaviour. Game crashed with #132 error on first launch, worked fine afterwards. -- 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=43656 --- Comment #6 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Issue is still present with Wine 2.18 (not staging). -- 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=43656 Matt Spraggs <matthew.spraggs(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthew.spraggs(a)gmail.com --- Comment #7 from Matt Spraggs <matthew.spraggs(a)gmail.com> --- Are others finding that updating to wine 2.20-staging fixes the issue as it did for me? -- 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=43656 --- Comment #8 from Matt Spraggs <matthew.spraggs(a)gmail.com> --- Seems I spoke too soon. Whilst 2.20-staging increases my success rate when launching the game from Battle.net, it still fails three times out of four, roughly. -- 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=43656 --- Comment #9 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Still present with wine 3.2. Bug 44370 may be duplicate or related. -- 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=43656 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 44370 has been marked as a duplicate of this bug. *** -- 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=43656 Chris Rankin <rankincj(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rankincj(a)yahoo.com --- Comment #11 from Chris Rankin <rankincj(a)yahoo.com> --- I've been playing WoW just fine for months with 2.20-Staging. It was only when Fedora updated to 3.1 (end of February 2018) that I started getting the "Game Initialization Failed" error. I do remember a brief period some time back when I'd previously experienced "Game Initialization failed" problems, but I thought that had been fixed. -- 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=43656 --- Comment #12 from Sveinar Søpler <cybermax(a)dexter.no> --- World of Warcraft does not work with "release" or "dev" version of wine - eg. 3.1+ You need to use wine-staging-2.21 (2.16-2.21 should work), or you can have a go at compiling your own staging version with the non-official staging from: https://github.com/wine-staging/wine-staging -- 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=43656 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net Component|-unknown |ntdll Ever confirmed|0 |1 URL| |https://eu.battle.net/accou | |nt/download/ Keywords| |download, obfuscation Status|UNCONFIRMED |NEW Summary|World of Warcraft crash on |64-bit World of Warcraft |startup with stack overflow |client reports 'Game | |Initialization Failed!' or | |crashes on startup with | |stack overflow due to | |improper mapping of | |exception code --- Comment #13 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, confirming. Relevant part of trace log: --- snip --- $ pwd /home/focht/wine-games/wineprefix64-bnet/drive_c/Program Files (x86)/World of Warcraft $ WINEDEBUG=+seh,+relay,+ntdll wine ./Wow-64.exe >>log2.txt 2>&1 ... 002a:Call TLS callback (proc=0x1400039c0,module=0x140000000,reason=PROCESS_ATTACH,reserved=0) 002a:Call KERNEL32.VirtualProtect(14129b430,00000110,00000004,0023e468,) ret=140004f3e 002a:Ret KERNEL32.VirtualProtect() retval=00000001 ret=140004f3e 002a:Call KERNEL32.VirtualProtect(14129b430,00000110,00000002,0023e480,) ret=1400051da 002a:Ret KERNEL32.VirtualProtect() retval=00000001 ret=1400051da 002a:Ret TLS callback (proc=0x140373710,module=0x140000000,reason=PROCESS_ATTACH,reserved=0) 002a:Call TLS callback (proc=0x14000e530,module=0x140000000,reason=PROCESS_ATTACH,reserved=0) 002a:Call ntdll.RtlAddVectoredExceptionHandler(00000001,14002f870,) ret=14000c52b 002a:Ret ntdll.RtlAddVectoredExceptionHandler() retval=000419c0 ret=14000c52b 002a:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x14000c5df ip=14000c5df tid=002a 002a:trace:seh:NtRaiseException rax=0000000000000055 rbx=0000000000000000 rcx=000000007bdb321f rdx=000000007bdb31d0 002a:trace:seh:NtRaiseException rsi=000000007bd97758 rdi=0000000000003a68 rbp=000000000023dd70 rsp=000000000023dd20 002a:trace:seh:NtRaiseException r8=0000000000000009 r9=000000014000c52b r10=0000000000000000 r11=0000000000000246 002a:trace:seh:NtRaiseException r12=00000000fd25be65 r13=0000000000000000 r14=000000007bd95170 r15=000000007bd98a4c 002a:trace:seh:call_vectored_handlers calling handler at 0x14002f870 code=c0000005 flags=0 002a:trace:seh:call_vectored_handlers handler at 0x14002f870 returned 0 002a:trace:seh:RtlVirtualUnwind type 1 rip 14000c5df rsp 23dd20 002a:trace:seh:dump_unwind_info **** func c030-e52d 002a:trace:seh:dump_unwind_info unwind info at 0x14150e9bc flags 0 prolog 0xf7 bytes function 0x14000c030-0x14000e52d 002a:trace:seh:dump_unwind_info 0xf7: movq %r15,0x28(%rsp) 002a:trace:seh:dump_unwind_info 0xec: movq %r14,0x30(%rsp) 002a:trace:seh:dump_unwind_info 0xe7: movq %rdi,0x38(%rsp) 002a:trace:seh:dump_unwind_info 0xde: movq %rsi,0x40(%rsp) 002a:trace:seh:dump_unwind_info 0xd9: movq %rbx,0x48(%rsp) 002a:trace:seh:dump_unwind_info 0x16: subq $0x50,%rsp 002a:trace:seh:dump_unwind_info 0xf: pushq %r13 002a:trace:seh:dump_unwind_info 0xd: pushq %r12 002a:trace:seh:dump_unwind_info 0xb: pushq %rbp 002a:trace:seh:RtlVirtualUnwind type 1 rip 14000f2cb rsp 23dd90 002a:trace:seh:dump_unwind_info **** func e5a0-1562d 002a:trace:seh:dump_unwind_info unwind info at 0x14150e9f4 flags 0 prolog 0x30 bytes function 0x14000e5a0-0x14001562d ... 002a:trace:seh:call_stack_handlers found wine frame 0x23e630 rsp 23e790 handler 0x7bd4a517 002a:trace:seh:call_teb_handler calling TEB handler 0x7bd4a517 (rec=0x23dbe0, frame=0x23e630 context=0x23ce90, dispatch=0x23d360) ... 002a:trace:seh:RtlRestoreContext returning to 7bd4a290 stack 23e620 002a:exception in TLS callback (proc=0x14129b438,module=0x140000000,reason=PROCESS_ATTACH,reserved=0) 002a:Starting process L"C:\\Program Files (x86)\\World of Warcraft\\Wow-64.exe" (entryproc=0x1400b4f50) 002a:trace:ntdll:NtQueryInformationProcess (0xffffffffffffffff,0x00000007,0x23fda8,0x00000008,(nil)) 002a: get_process_info( handle=ffffffff ) 002a: get_process_info() = 0 { pid=0029, ppid=0000, affinity=000000ff, peb=7fffffeaf000, start_time=1d3b2efbed2f538 (-0.0964970), end_time=0, exit_code=259, priority=2, cpu=x86_64, debugger_present=0, debug_children=1 } 002a:Call user32.MessageBoxW(00000000,0023fd10 L"Game Initialization Failed!",0023fd00 L"ERROR",00000010,) ret=1400b55ec ... --- snip --- The actual problem is not visible. One has to debug the code in the TLS callbacks which is another problem as 'winedbg' can't do this (unless one hacks Wine). This is were 'x64dbg' (https://x64dbg.com/) comes handy which allows to stop in TLS callbacks before the entry point is called. Unfortunately it's also ridden with a number of Wine bugs that have to be worked around to be somewhat usable. During execution of the second TLS callback, a vectored exception handler is installed which ought to handle privileged instructions and set trap flag to cause single step events. --- snip --- ... 000000014000C511 48 05 89 .. add rax, FFFFFFFFFFFFF989 000000014000C517 48 89 45 .. mov qword ptr ss:[rbp+30], rax 000000014000C51B 48 8B 05 .. mov rax, qword ptr ds:[141813C50] 000000014000C522 48 8B 55 .. mov rdx, qword ptr ss:[rbp+30] 000000014000C526 49 33 C1 xor rax, r9 000000014000C529 FF D0 call rax ; ntdll.RtlAddVectoredExceptionHandler 000000014000C52B 48 89 05 .. mov qword ptr ds:[1418D6C00], rax 000000014000C532 48 85 C0 test rax, rax 000000014000C535 0F 84 CD .. je wow-64.14000E508 000000014000C53B 48 89 5D .. mov qword ptr ss:[rbp+30], rbx ... 000000014000C5D7 0F B6 45 .. movzx eax, byte ptr ss:[rbp+30] 000000014000C5DB 84 C0 test al, al 000000014000C5DD 74 B4 je wow-64.14000C593 000000014000C5DF F4 hlt ; <---- EXCEPTION_PRIV_INSTRUCTION 000000014000C5E0 4C 8B 5D .. mov r11, qword ptr ss:[rbp+20] ... --- snip --- Unfortunately Wine's exception handling maps the 'hlt' instruction to EXCEPTION_ACCESS_VIOLATION which leads to a different code path in vectored handler which later leads to things going haywire. It seems there was a typo introduced by: https://source.winehq.org/git/wine.git/commitdiff/e1d68b2e169580be8dc6f8927e... ("ntdll: Implement handling of int $0x2d for x86_64.") https://source.winehq.org/git/wine.git/blob/39c8875ff8aa543eaa50e52db0c54671... --- snip --- 2750 static void segv_handler( int signal, siginfo_t *siginfo, void *sigcontext ) 2751 { 2752 EXCEPTION_RECORD *rec; 2753 ucontext_t *ucontext = sigcontext; ... 2770 rec = setup_exception( sigcontext, raise_segv_exception ); 2771 if (rec->ExceptionCode == EXCEPTION_STACK_OVERFLOW) return; 2772 2773 switch(TRAP_sig(ucontext)) 2774 { ... 2789 case TRAP_x86_UNKNOWN: /* Unknown fault code */ 2790 { 2791 CONTEXT *win_context = get_exception_context( rec ); 2792 WORD err = ERROR_sig(ucontext); 2793 if ((err & 7) == 2 && handle_interrupt( err >> 3, rec, win_context )) break; 2794 rec->ExceptionCode = err ? EXCEPTION_ACCESS_VIOLATION : EXCEPTION_PRIV_INSTRUCTION; 2795 rec->ExceptionCode = EXCEPTION_ACCESS_VIOLATION; 2796 } 2797 break; --- snip --- Line 2795 has to be removed. Fixing this will likely fix a number of apps and games that depend on proper privileged instruction handling (part of DRM schemes -> decrypt, anti-debugging etc.). NOTE: With this fix applied the entry point is successfully reached and the client runs further but ends up in other bugs I've already documented for Diablo III (bug 44585 , bug 44616 , bug 44617) $ wine --version wine-3.3 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.
https://bugs.winehq.org/show_bug.cgi?id=43656 --- Comment #14 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Unfortunately, I'm not running the 64 bit client but the 32 bit client in a 32 bit wineprefix. Removing the "rec->ExceptionCode = EXCEPTION_ACCESS_VIOLATION;" line from segv_handler() in dlls/ntdll/signal_x86_64.c did not fix the issue. segv_handler() in dlls/ntdll/signal_i386.c has nothing wrong, as far as I can tell. -- 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=43656 --- Comment #15 from Anastasius Focht <focht(a)gmx.net> --- Hello, --- quote --- Unfortunately, I'm not running the 64 bit client but the 32 bit client in a 32 bit wineprefix. Removing the "rec->ExceptionCode = EXCEPTION_ACCESS_VIOLATION;" line from segv_handler() in dlls/ntdll/signal_x86_64.c did not fix the issue. --- quote --- Well, the 32-bit WoW version shares the same issues as the 64-bit version afterwards. Quoting myself: --- quote --- NOTE: With this fix applied the entry point is successfully reached and the client runs further but ends up in other bugs I've already documented for Diablo III (bug 44585 , bug 44616 , bug 44617) --- quote --- It would be automatically a dupe of one of the other tickets. If you prefer 32-bit here I move all my analysis/comments to bug 44370 (which had at least one comment on 64-bit) and resolve this as dupe. 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.
https://bugs.winehq.org/show_bug.cgi?id=43656 --- Comment #16 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- The typo is already fixed in staging [1]. (In reply to Anastasius Focht from comment #15)
NOTE: With this fix applied the entry point is successfully reached and the client runs further but ends up in other bugs I've already documented for Diablo III (bug 44585 , bug 44616 , bug 44617)
Since every bug seems to be staged, I tried applying all the staging patchsets, but I still get the 'Game Initialization Failed!' error. I don't know what I'm missing here. [1] https://github.com/wine-staging/wine-staging/blob/master/patches/ntdll-x86_6... -- 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=43656 William Panlener <wpanlener(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wpanlener(a)gmail.com --- Comment #17 from William Panlener <wpanlener(a)gmail.com> --- This should be resolved by https://source.winehq.org/git/wine.git/commitdiff/2f870c1801c8d455faadd6c301... -- 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=43656 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |2f870c1801c8d455faadd6c301a | |ad318f287713b Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #18 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, fixed by commit https://source.winehq.org/git/wine.git/commitdiff/2f870c1801c8d455faadd6c301... Thanks Sebastian It will still crash/report problems but that's due to aforementioned bug(s) with staged patches still missing and additional ones, not yet explicitly tracked. I don't see the point of completely revealing everything as of now. I did these bug-chains many times in the past with the result that people would just pick the low hanging fruits from the chain and not bother with the rest. So we simply play the game of bug-by-bug. Bug resolved? You get the next one explained. Simple. Anyway, if you are blocked and need to run an app/game just use Wine-Staging. 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.
https://bugs.winehq.org/show_bug.cgi?id=43656 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #19 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.4. -- 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=43656 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|CLOSED |REOPENED --- Comment #20 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Reopening since it still crashes for me with wine 3.4(stack overflow) and wine-staging 3.4(Game Initialization Failed"). Stack overflow with wine 3.4 is expected, but with staging it's expected to work and it does not(for me). I'm using 32 bit WoW client. Battle.net works fine with staging. I'm not going to file another bug, because I'm the OP and nothing was fixed for me since I reported the bug. -- 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=43656 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|64-bit World of Warcraft |32-bit World of Warcraft |client reports 'Game |client reports 'Game |Initialization Failed!' or |Initialization Failed!' or |crashes on startup with |crashes on startup with |stack overflow due to |stack overflow |improper mapping of | |exception code | -- 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=43656 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #59089|0 |1 is obsolete| | --- Comment #21 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Created attachment 60807 --> https://bugs.winehq.org/attachment.cgi?id=60807 log wine-staging 3.4 +seh,+relay,+ntdll (compressed) Same kind of exception in TLS callback: --- start log --- ... 0009:Call TLS callback (proc=0x40d8a0,module=0x400000,reason=PROCESS_ATTACH,reserved=0) 0009:Call ntdll.RtlAddVectoredExceptionHandler(00000001,0042ac80) ret=0040bcbb 0009:Ret ntdll.RtlAddVectoredExceptionHandler() retval=00117a50 ret=0040bcbb 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40bda0 ip=0040bda0 tid=0009 0009:trace:seh:raise_exception eax=00006267 ebx=7bd111a5 ecx=00006bea edx=00000000 esi=00000162 edi=00000000 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e308 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010293 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40c0fd ip=0040c0fd tid=0009 0009:trace:seh:raise_exception eax=000000cc ebx=7b63e93d ecx=7b423258 edx=7b63b1a4 esi=7b420000 edi=00000000 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e308 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40c4a4 ip=0040c4a4 tid=0009 0009:trace:seh:raise_exception eax=236e6246 ebx=7b643a10 ecx=00000000 edx=7b63b1a4 esi=0000048c edi=00000000 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e308 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010297 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40c8f0 ip=0040c8f0 tid=0009 0009:trace:seh:raise_exception eax=40c65139 ebx=7bd0ff35 ecx=00000000 edx=00000000 esi=7b420000 edi=00000000 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e308 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010206 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40cc7e ip=0040cc7e tid=0009 0009:trace:seh:raise_exception eax=00000024 ebx=7b641e1a ecx=7b426b88 edx=7b63b1a4 esi=7b420000 edi=00000000 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e308 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010297 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40d071 ip=0040d071 tid=0009 0009:trace:seh:raise_exception eax=56d3906f ebx=7b420000 ecx=3bc81dfe edx=00000000 esi=00000000 edi=00000000 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e308 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010293 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40d709 ip=0040d709 tid=0009 0009:trace:seh:raise_exception eax=4b6f5401 ebx=7bd1304f ecx=2dd41343 edx=00000000 esi=00000012 edi=001105b8 0009:trace:seh:raise_exception ebp=0033e340 esp=0033e310 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010216 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:trace:seh:raise_exception code=c0000096 flags=0 addr=0x40f15b ip=0040f15b tid=0009 0009:trace:seh:raise_exception eax=b18dfbeb ebx=0033e9f4 ecx=0033e7df edx=00400000 esi=00000398 edi=00000010 0009:trace:seh:raise_exception ebp=0033e9e0 esp=0033e350 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010213 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000096 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned ffffffff 0009:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0x40f7c1 ip=0040f7c1 tid=0009 0009:trace:seh:raise_exception info[0]=00000000 0009:trace:seh:raise_exception info[1]=7ffd6060 0009:trace:seh:raise_exception eax=00000060 ebx=0033e9f4 ecx=7ffd8000 edx=00000006 esi=00000001 edi=7ffd6000 0009:trace:seh:raise_exception ebp=0033e9e0 esp=0033e350 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010217 0009:trace:seh:call_vectored_handlers calling handler at 0x42ac80 code=c0000005 flags=0 0009:trace:seh:call_vectored_handlers handler at 0x42ac80 returned 0 0009:trace:seh:call_stack_handlers calling handler at 0x7bccd690 code=c0000005 flags=0 0009:trace:seh:__regs_RtlUnwind code=c0000005 flags=2 0009:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7bd0bd8c ecx=0033e2f8 edx=0033ea5c esi=0033ea5c edi=7bccd500 0009:trace:seh:__regs_RtlUnwind ebp=0033deb8 esp=0033de98 eip=7bccd55c cs=0023 ds=002b fs=0063 gs=006b flags=00000206 0009:trace:seh:__regs_RtlUnwind calling handler at 0x7bca6b80 code=c0000005 flags=2 0009:trace:seh:__regs_RtlUnwind handler at 0x7bca6b80 returned 1 0009:exception in TLS callback (proc=0x1080308,module=0x400000,reason=PROCESS_ATTACH,reserved=0) 0009:Starting process L"C:\\Program Files\\World of Warcraft\\Wow.exe" (entryproc=0x4afb10) 0009:trace:ntdll:NtQueryInformationProcess (0xffffffff,0x00000007,0x33febc,0x00000004,(nil)) 0009:Call user32.MessageBoxW(00000000,0033fe10 L"Game Initialization Failed!",0033fe54 L"ERROR",00000010) ret=004b0123 ... --- end log --- It seems that none of the wine-staging patches fixes my issue. I've downloaded x64dbg but don't know how to use it yet. I've also changed the summary of the bug because although the 64-bit analysis and fix are correct, it's not my issue. -- 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=43656 --- Comment #22 from Anastasius Focht <focht(a)gmx.net> --- Hello, ok ... then have it your way. I'm sorry that I apparently "hijacked" your ticket. I will not bother with your tickets again. You might find someone else to explain the missing bits and pieces. It's not super hard for someone experienced but still takes some effort to provide proper analysis of the remaining problems. 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.
https://bugs.winehq.org/show_bug.cgi?id=43656 Matt Spraggs <matthew.spraggs(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|matthew.spraggs(a)gmail.com | -- 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=43656 --- Comment #23 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Bug still present with wine-staging 3.8. -- 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=43656 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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=43656 --- Comment #24 from Ker noa <blue-t(a)web.de> --- Battle for Azeroth will get rid of 32bit support (and dx9), so this bug will be redundant by then. Is it worth keeping it open? -- 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=43656 --- Comment #25 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Ker noa from comment #24)
Battle for Azeroth will get rid of 32bit support (and dx9), so this bug will be redundant by then. Is it worth keeping it open?
I didn't knew that. I'll test the 64 bit client and if it's not affected by this bug I'll close it myself. -- 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=43656 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED Status|REOPENED |RESOLVED --- Comment #26 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- I could play with the 64 bit client and wine-staging 3.8 without issues. I reinstalled the 32 bit version in a clean wine prefix to be sure: Still gives 'Game Initialization Failed!' error. Marking ABANDONED. -- 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=43656 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de Status|RESOLVED |CLOSED --- Comment #27 from André H. <nerv(a)dawncrow.de> --- closing abandoned -- 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)
-
wine-bugs＠winehq.org