Wine-bugs

Download

wine-bugs@list.winehq.org

July 2021

1 participants
5732 discussions

[Bug 39738] New: Collecting backtrace of crashing process not possible.
by wine-bugs＠winehq.org 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=39738 Bug ID: 39738 Summary: Collecting backtrace of crashing process not possible. Product: Wine Version: 1.8-rc2 Hardware: x86-64 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50183/Alarm_fuer_Cobra_11_Burning_Wheel s/Deutsche_Demo.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)vr-web.de Distribution: Debian Created attachment 52997 --> https://bugs.winehq.org/attachment.cgi?id=52997 On crash stop all other threads before executing winedbg. This is about a crash in "Cobra 11 - Burning Wheels" demo. It seems this demo includes parts of the copy protection of the full game. (see https://bugs.winehq.org/show_bug.cgi?id=39734 ) Therefore it is not possible to start it with winedbg from begin. Also one gets the crash dialog, but clicking on details shows just "Loading detailed information, please wait...". With the crash dialog disabled it shows: wine: Unhandled page fault on read access to 0x1adb2920 at address 0x52f7b2 (thread 0009), starting debugger... Process of pid=0008 has terminated No process loaded, cannot execute 'echo Modules:' Cannot get info on module while no process is loaded No process loaded, cannot execute 'echo Threads:' (remaining threads) winedbg: Internal crash at 0x7ed8af1d Attaching plain gdb makes the process not end itself and the process gets stopped on the crash. But setting breakpoints is not possible without "disturbing" the process. The attached patch assumes that just one thread crashes which starts then winedbg. Meanwhile another thread gets notified about the crash and terminates the process before winedbg gets a chance to attach. Therefore this patch tries to suspend all other threads before starting winedbg. That way the crash dialog could show a backtrace reliably. -- 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.

2 4

[Bug 39734] New: ProtectDisc Driver 11: acedrv11.sys crashes
by wine-bugs＠winehq.org 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=39734 Bug ID: 39734 Summary: ProtectDisc Driver 11: acedrv11.sys crashes Product: Wine Version: 1.8-rc2 Hardware: x86-64 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50183/Alarm_fuer_Cobra_11_Burning_Wheel s/Deutsche_Demo.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)vr-web.de Distribution: Debian Created attachment 52986 --> https://bugs.winehq.org/attachment.cgi?id=52986 backtrace.txt The demo version of "Cobra 11: Burning Wheels" comes with this copy protection driver. It gets silently installed by default. One can extract the protection driver from the setup with: 7z x BurningWheelsDemo.exe "\$PLUGINSDIR/Driver_Setup.exe" After this driver is installed wine tries to start the copy protection driver acedrv11.sys on every startup of this wineprefix. This results in a crash of this driver: bernhard(a)rechner:~/wine/drive_c$ wineserver -k; wine wineboot fixme:ntoskrnl:IoGetDeviceObjectPointer stub: L"\\DosDevices\\CdRom0" 80 0x53e690 0x53e694 fixme:ntoskrnl:KeInitializeEvent stub: 0x11264c 0 0 wine: Unhandled page fault on read access to 0x00000060 at address 0x57923a (thread 0019), starting debugger... ProtectionID v0.6.7.0 identifies it as: #[VersionInfo] Product Name : ProtectDisc x64/x86 Hybrid Driver #[VersionInfo] Product Version : 9.0.0.0 #[VersionInfo] File Version : 11.0.0.11 built by: WinDDK #[VersionInfo] Original FileName : acedrv.sys #[!] ProtectDisc v 9.0.0.0 Driver -- 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.

2 21

Jump to page: