[Bug 48788] null pointer in wined3d_palette_set_entries with Diablo GOG

[WineHQ Bugzilla]

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

--- Comment #3 from Per Christian Henden <perchrh-wine at pvv.org> ---
Thank you Paul for the detailed investigation, summary and patch!

I'm pondering how Windows handles this. Perhaps it's just luck that the
application doesn't crash even though it writes outside of the surface data
area. Maybe Windows keeps two surface data areas next to each other in memory
for double buffering or so? 
It wasn't just one byte/element size outside? If it's just one or two, I
thought maybe it's an alignment issue or off-by-one bug in Wine. 
This topic isn't my forte, but I thought I'd try to contribute with some
thoughts :)


A partially displayed menu is a step forward :)
Did selecting the menu items work?
I read that in another case/version the menu was a bit off, but the game could
still be played.

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