http://bugs.winehq.org/show_bug.cgi?id=32014
BitMaster spamzooi1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #42199|0 |1 is obsolete| |
--- Comment #8 from BitMaster spamzooi1@gmail.com 2012-10-20 07:25:00 CDT --- Created attachment 42201 --> http://bugs.winehq.org/attachment.cgi?id=42201 Memory dump generated by BL2 with wine debug symbols
This one should be with wine debug symbols. I'm actually not sure in which case this dump is generated. Is there any proper guide on how to debug this?
I tried WINEDEBUG=+relay and it generates a HUGE log with on the end only calls about critical sections and sleeps. Does this mean some kind of deadlock?
Also, the result is not everytime the same when running Borderlands2.exe. Sometimes Steam complaints about currently not being able to handle the request and sometimes the game stops/crashes in the middle of the intro videos (indentifyable by the interruption of the audio). Furthermore, if I adjust the resolution to the resolution BL2 uses, there is no black screen at all. I can't really recognize a pattern.