[Bug 43656] 64-bit World of Warcraft client reports ' Game Initialization Failed!' or crashes on startup with stack overflow due to improper mapping of exception code

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=43656

--- Comment #15 from Anastasius Focht <focht at 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.