[Bug 42217] New: d3d[89] tests/ device crash on i965 executing IDirect3D8_CreateDevice
https://bugs.winehq.org/show_bug.cgi?id=42217 Bug ID: 42217 Summary: d3d[89] tests/device crash on i965 executing IDirect3D8_CreateDevice Product: Wine Version: 2.0-rc5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 56857 --> https://bugs.winehq.org/attachment.cgi?id=56857 backtrace Crashes trying to execute an invalid float operation in 32-bit code. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42217 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- This seems to have been fixed upstream in mesa—after an upgrade from 11.2.0 to 12.0.6, I no longer get the crash. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42217 fjfrackiewicz(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz(a)gmail.com --- Comment #2 from fjfrackiewicz(a)gmail.com --- (In reply to Zebediah Figura from comment #1)
This seems to have been fixed upstream in mesa—after an upgrade from 11.2.0 to 12.0.6, I no longer get the crash.
Perhaps this bug should be reclassified as "notourbug" since the bug was in Mesa? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42217 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |NOTOURBUG --- Comment #3 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to fjfrackiewicz from comment #2)
(In reply to Zebediah Figura from comment #1)
This seems to have been fixed upstream in mesa—after an upgrade from 11.2.0 to 12.0.6, I no longer get the crash.
Perhaps this bug should be reclassified as "notourbug" since the bug was in Mesa?
Yes, you are probably right. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42217 --- Comment #4 from fjfrackiewicz(a)gmail.com --- BTW, does Mesa 17 affect this in any way? I noticed you have a slightly older version of Mesa hence my asking :) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42217 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Zebediah Figura from comment #1)
This seems to have been fixed upstream in mesa—after an upgrade from 11.2.0 to 12.0.6, I no longer get the crash.
Closing upstream as the bug was fixed in Mesa. -- 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.
participants (1)
-
wine-bugs＠winehq.org