https://bugs.winehq.org/show_bug.cgi?id=27439
--- Comment #85 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Zeb Figura from comment #80)
If it really is a matter of writing past mapped memory bounds, then an apitrace won't help.
Hello,
What if the out of bound writing results from bad expectations of the game related to DX operations? Wouldn't it be useful to understand what the game was trying to do at the time of the crash?
I would still find apitraces usefull: One from the game working on Windows, to confirm that the apitrace is not affected by those memory access issues; One from the game not working on Wine, to locate what the game was trying to do with memory in the sequence of DX operations.
I don't have any of the affected games. There is nothing much I can do for this bug. Some comments suggest that the issue relates to the game DX rendering engine, so I thought that apitraces could be used to check that and I suggested that.
(In reply to kenoi from comment #84)
I stand for being practical, not hopeless wishful thinking.
Really? With all due respect, you've come to the Wine bug tracker to rant about your opinion that the bug should not be fixed by the Wine project. How is that practical? Isn't that just trolling? If you're so persuaded of being right and want to be practical just go start your own Storm Engine fixing project and stop wasting other people's time with a pointless debate.
Regards.