http://bugs.winehq.org/show_bug.cgi?id=31518
Bug #: 31518 Summary: Tomb Raider 4 (GOG version) software rendering crashes Product: Wine Version: 1.5.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jonas.th@web.de Classification: Unclassified
Created attachment 41453 --> http://bugs.winehq.org/attachment.cgi?id=41453 Terminal output
Due to bug #31260 I tried the software mode of Tomb raider 4, hoping it would yield a usable game. Sadly, it crashes.
The last two terminal lines leading up to the final crash line are possibly related I guess. Terminal output & backtrace from the wine crash dialog is attached
http://bugs.winehq.org/show_bug.cgi?id=31518
--- Comment #1 from jonas.th@web.de 2012-08-22 10:30:28 CDT --- Created attachment 41454 --> http://bugs.winehq.org/attachment.cgi?id=41454 Backtrace info provided by wine crash tool
http://bugs.winehq.org/show_bug.cgi?id=31518
jonas.th@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #41454|0 |1 is obsolete| |
--- Comment #2 from jonas.th@web.de 2012-08-22 10:39:52 CDT --- Created attachment 41455 --> http://bugs.winehq.org/attachment.cgi?id=41455 Backtrace info (2)
I wasn't sure it actually had a proper screen resolution selected and tried again ensuring that was the case, it still crashes (albeit with a slightly different crash log).
The "X11DRV_ChangeDisplaySettingsEx No matching mode found" is gone now, but "fixme:ddraw:d3d_device_create Only one Direct3D device per DirectDraw object supported." remains the last line right in front of the crash itself.
http://bugs.winehq.org/show_bug.cgi?id=31518
--- Comment #3 from Austin English austinenglish@gmail.com 2012-08-22 12:21:28 CDT ---
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1x124x0 @0! (XF86VidMode)
seems suspicious.
http://bugs.winehq.org/show_bug.cgi?id=31518
jonas.th@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #41453|0 |1 is obsolete| |
--- Comment #4 from jonas.th@web.de 2012-08-22 12:37:04 CDT --- Created attachment 41457 --> http://bugs.winehq.org/attachment.cgi?id=41457 Terminal output (2) with correct video mode selection
There seems to be an other issue with the video mode selection box which had no video mode preselected, when "fixing" this by selecting one, this x11 error goes away. However, it still crashes afterwards.
Attaching new terminal output (with properly selected video mode) to avoid further confusion.
http://bugs.winehq.org/show_bug.cgi?id=31518
kinodont@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kinodont@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=31518
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #41455|0 |1 is obsolete| | Attachment #41457|0 |1 is obsolete| | Status|UNCONFIRMED |NEW Assignee|wine-bugs@winehq.org |wylda@volny.cz Ever confirmed|0 |1
--- Comment #5 from Wylda wylda@volny.cz --- Created attachment 47247 --> http://bugs.winehq.org/attachment.cgi?id=47247 Crashlog from wine-1.7.11
I'm able to reproduce the issue in wine-1.7.11. The problem is reproducible, when under SW renderer mode i want also to play video (option "No FMV" is UNchecked). See http://bugs.winehq.org/show_bug.cgi?id=31260#c15
Crash log attached, console log:
fixme:int:__wine_emulate_instruction mov %cr4, %eax at 0x0048da53 fixme:int:__wine_emulate_instruction mov %cr4, %eax at 0x0048da64 fixme:win:EnumDisplayDevicesW ((null),0,0x33f640,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f330,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f3f0,0x00000000), stub! fixme:ddraw:d3d_device_create Only one Direct3D device per DirectDraw object supported. wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 0027), starting debugger...
http://bugs.winehq.org/show_bug.cgi?id=31518
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Tomb Raider 4 (GOG version) |Tomb Raider 4 crashes when |software rendering crashes |playing video (FMV) under | |software rendering mode
http://bugs.winehq.org/show_bug.cgi?id=31518
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|wylda@volny.cz |wine-bugs@winehq.org
https://bugs.winehq.org/show_bug.cgi?id=31518
--- Comment #6 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=31518
andy andy86@fastwebnet.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andy86@fastwebnet.it
--- Comment #7 from andy andy86@fastwebnet.it --- Hello.
Bug is still present in wine 1.7.55, back traces is same at that already posted.
First part of stack trace referred to binkw32.dll:
Modules: Module Address Debug info Name (102 modules) PE 400000- 813000 Deferred tomb4 PE 10000000-10057000 Deferred binkw32 ELF 785ab000-7a800000 Deferred libnvidia-glcore.so.358.16
Thank-you for your work.
https://bugs.winehq.org/show_bug.cgi?id=31518
--- Comment #8 from andy andy86@fastwebnet.it --- Hello.
I've try with winedbg, at moment of the crash i've find this:
<i> wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 0095), starting debugger... Invalid address (0x7b869ce2 call_process_entry+0x14e) for breakpoint 0, disabling it</i>
With "WINEDEBUG=+relay" the last call before the crash seems be:
<i> 005c:Call user32.FindWindowA(004bce04 "DBLogWindowClass",004bce18 "DBLog Server") ret=0049c767 005c:Ret user32.FindWindowA() retval=00000000 ret=0049c767</i>
If needed, i can attach full backtrace.
https://bugs.winehq.org/show_bug.cgi?id=31518
--- Comment #9 from Bruno Jesus 00cpxxx@gmail.com --- Many games are now available for download at archive.org, this is one of them and the problem is still present in wine 1.9.11:
https://archive.org/details/Tomb_Raider_4_The_Last_Revelation_-_Windows95_Ei...
https://bugs.winehq.org/show_bug.cgi?id=31518
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #10 from joaopa jeremielapuree@yahoo.fr --- Confirming with vanilla wine 4-9. Problem is obvious 0042:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0051:fixme:int:__wine_emulate_instruction mov %cr4, %eax at 0x0048d843 0051:fixme:int:__wine_emulate_instruction mov %cr4, %eax at 0x0048d854 0051:fixme:win:EnumDisplayDevicesW ((null),0,0x32f0b8,0x00000000), stub! 0051:fixme:win:EnumDisplayDevicesW ((null),0,0x32ee18,0x00000000), stub! 0051:fixme:win:EnumDisplayDevicesW ((null),0,0x32f378,0x00000000), stub! 0059:fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 0059:fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 0059:fixme:ddraw:d3d_device_create Only one Direct3D device per DirectDraw object supported. wine: Unhandled page fault on read access to 0x00000001 at address 0x7ddb72c1 (thread 0059), starting debugger...
Can an administrator close this bug as duplicate of bug 24308 .
-
wine-bugs＠winehq.org