http://bugs.winehq.org/show_bug.cgi?id=21172
Summary: Counter strike 1.6 crashes with ATI Catalyst 9.12 driver Product: Wine Version: 1.1.35 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: petoju@gmail.com
Created an attachment (id=25420) --> (http://bugs.winehq.org/attachment.cgi?id=25420) Backtrace of the crash
Counter strike crashes, on startup, when selecting something from menu or when clicking anything in options (depending on registry setup). It is not possible to try older drivers as long as I am not able to get their installers.
According to backtrace, crash is caused by fglrx_dri.so and zero-division: Unhandled exception: divide by zero in 32-bit code (0x7a77b1d0).
Tested on: Ubuntu 9.10 AMD64 Wine 1.1.34-35 ATI Catalyst 9.12
Under AppDB page of Counter strike 1.6, mmichel describes possibly similar bug with Gentoo AMD64 Wine 1.1.31 ati-drivers' version is marked as 9.9 in gentoo portage
http://bugs.winehq.org/show_bug.cgi?id=21172
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com 2009-12-27 15:48:03 --- First of all don't do this: --- PE 65340000-653d2000 Deferred oleaut32 PE 65f00000-65fc2000 Deferred ole32 PE 70100000-70153000 Deferred rpcrt4 --- or at least specify why do you need it.
Anyway it crashes on driver code. Report this to AMD/ATI.
http://bugs.winehq.org/show_bug.cgi?id=21172
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Nikolay Sivov bunglehead@gmail.com 2009-12-27 15:48:17 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=21172
Peter petoju@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #25420|0 |1 is obsolete| |
--- Comment #3 from Peter petoju@gmail.com 2009-12-27 15:54:03 --- Created an attachment (id=25421) --> (http://bugs.winehq.org/attachment.cgi?id=25421) Second backtrace, without native libraries
http://bugs.winehq.org/show_bug.cgi?id=21172
--- Comment #4 from Peter petoju@gmail.com 2009-12-27 16:09:44 --- Replies under questions:
(In reply to comment #1)
First of all don't do this: ... or at least specify why do you need it.
I wanted it to run, so I tried native libs.
(In reply to comment #1)
Anyway it crashes on driver code. Report this to AMD/ATI.
But wine crashes, so I should report it also here. It is already reported to AMD/ATI.
http://bugs.winehq.org/show_bug.cgi?id=21172
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2009-12-27 23:39:46 --- (In reply to comment #4)
Anyway it crashes on driver code. Report this to AMD/ATI.
But wine crashes, so I should report it also here. It is already reported to AMD/ATI.
Backtrace: =>0 0x7a77b1d0 in fglrx_dri.so (+0x8d41d0) (0x00000000)
It is not Wine who crashes.
http://bugs.winehq.org/show_bug.cgi?id=21172
--- Comment #6 from Peter petoju@gmail.com 2009-12-28 03:46:54 --- And what about workaround in Wine?
With every different config, Counter strike 1.6 does not produce backtrace that can help or say that bug is made by AMD/ATI.
http://bugs.winehq.org/show_bug.cgi?id=21172
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2009-12-28 04:10:34 --- (In reply to comment #6)
And what about workaround in Wine?
Which workaround? Workaround for what? If you mean that Wine should workaround bugs in video drivers, that's not how it's supposed to work. Do you report Wine bugs to Windows application developers asking for a workaround?
With every different config, Counter strike 1.6 does not produce backtrace that can help or say that bug is made by AMD/ATI.
That's what the bug reporting system is for. You report a problem -> a knowledgeable person investigates it, and makes a decision.
http://bugs.winehq.org/show_bug.cgi?id=21172
--- Comment #8 from Peter petoju@gmail.com 2009-12-28 05:14:04 --- (In reply to comment #7)
(In reply to comment #6)
And what about workaround in Wine?
Which workaround? Workaround for what? If you mean that Wine should workaround bugs in video drivers, that's not how it's supposed to work.
I request workaround/fix, because Wine sends drivers parameters, that crash it. Are you sure Wine does not send such parameters?
(In reply to comment #7)
Do you report Wine bugs to Windows application developers asking for a workaround?
I report it to Wine because as seen by me only Wine is affected by different drivers. When everyone can use it without bug, why Wine can't?
http://bugs.winehq.org/show_bug.cgi?id=21172
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2009-12-28 09:10:05 --- (In reply to comment #8)
I request workaround/fix, because Wine sends drivers parameters, that crash it. Are you sure Wine does not send such parameters?
Wine doesn't interact directly with video drivers.
Do you report Wine bugs to Windows application developers asking for a workaround?
I report it to Wine because as seen by me only Wine is affected by different drivers. When everyone can use it without bug, why Wine can't?
Wine uses system OpenGL libraries. If those libraries make your video driver crash why that's a Wine problem?
If you suspect a Wine bug, then write a test case for that behaviour.
-
wine-bugs＠winehq.org