[Bug 48788] New: null pointer in wined3d_palette_set_entries with Diablo GOG
WineHQ Bugzilla
wine-bugs at winehq.org
Sun Mar 22 10:30:29 CDT 2020
https://bugs.winehq.org/show_bug.cgi?id=48788
Bug ID: 48788
Summary: null pointer in wined3d_palette_set_entries with
Diablo GOG
Product: Wine
Version: 5.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs at winehq.org
Reporter: perchrh-wine at pvv.org
Distribution: ---
Created attachment 66691
--> https://bugs.winehq.org/attachment.cgi?id=66691
WINEDEBUG=+d3d wine Diablo.exe
The game "Diablo", appdb-link: [1] crashes on startup due to a wine_d3d error.
Steps to reproduce:
1 Set the wine configuration to Windows 10, virtual desktop 800x600, to make
the installer work.
2 Run the GOG Diablo installer,
'wine setup_diablo_1.09_hellfire_v2_(30038).exe'
3 Then in the game directory, run 'wine Diablo.exe', to launch the game.
After launching the game, the Blizzard logo successfully shows on screen.
Immediately after the logo animation, wine crashes.
The crash looks like a null pointer, excerpt below:
Backtrace:
=>0 0x7c52d82e wined3d_palette_set_entries+0x3e() in wined3d (0x0032fc38)
0x7c52d82e wined3d_palette_set_entries+0x3e in wined3d: movl 0x0(%eax),%ecx
The attached log with WINEDEBUG=+d3d show wined3d_palette_set_entries is first
successfully called multiple times before the null pointer crash. The logs are
from a clean wine prefix. The crash is reproducible 100% of the time. I had to
run wineserver -k after the crash to launch the game again.
This crash differs from the other startup bug registered for the same game [2],
which crashes in storm.dll as opposed to wine_d3d.
[1]
https://appdb.winehq.org/objectManager.php?sClass=version&iId=37759
[2]
https://bugs.winehq.org/show_bug.cgi?id=46803
--
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.
More information about the wine-bugs
mailing list