[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.

[WineHQ Bugzilla]

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

--- Comment #12 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Sveinar Søpler from comment #11)
> Yep. But you would only end up with a staging patch commit anyway, cos it is
> not that easy to bisect wine when needing staging. (Atleast not for me). Ie.
> Lets say i take a random git pull of wine, and try to apply staging to that
> it will fail.
> 
> So you would end up with a certain commit of staging causing a regression,
> but the commit COULD still be in wine, and somewhat harder to find out as
> its not "just" reverting patches of wine without breaking staging.
> 
> Then again, i am not that pro, so it could be easy for those in the know :)

Yes, that's why, as the instructions say, you want to first identify the
minimal subset of Staging patches that are necessary to allow the application
to run. That takes every other patch out of the equation, and also means they
won't be a problem when trying to apply patches.

-- 
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.