https://bugs.winehq.org/show_bug.cgi?id=27439
--- Comment #87 from Zeb Figura z.figura12@gmail.com --- (In reply to Olivier F. R. Dierick from comment #85)
(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.
As I understand, apitrace only records memory within the bounds of the actual map. It won't actually tell us whether the application is writing outside of the map bounds on Windows; the actual trace should presumably succeed either way.