[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 #11 from Sveinar Søpler <cybermax at dexter.no> ---
(In reply to Zebediah Figura from comment #10)
> 
> The magic of bisections is that "many hundreds" still only means about ten
> steps ;-)
> 
> Anyway, yes, it's a lot of work, but someone has to do it, or you have to
> ask developers to solve this bug as if they knew nothing about it. Believe
> me when I say that's far more difficult.

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 :)

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