[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 Timothy Arceri changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 --- Comment #6 from Hi-Angel --- (In reply to Ian Romanick from comment #1) > Is it possible to get a backtrace from __glXSendError? I don't understand > why this particular commit would change behavior from "not error" to "error". Sure, can

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 Michel Dänzer changed: What|Removed |Added CC||zegen...@protonmail.com -- You are

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 Michel Dänzer changed: What|Removed |Added CC||hi-an...@yandex.ru --- Comment #5 from

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 --- Comment #4 from Andrew Randrianasulu --- (In reply to Andrew Randrianasulu from comment #2) > Created attachment 144184 [details] > apitrace from failed run (mesa git without revert) hm, last line from apitrace: 12665

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 --- Comment #3 from Andrew Randrianasulu --- (In reply to Ian Romanick from comment #1) > Is it possible to get a backtrace from __glXSendError? I don't understand > why this particular commit would change behavior from "not error" to "error".

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 --- Comment #2 from Andrew Randrianasulu --- Created attachment 144184 --> https://bugs.freedesktop.org/attachment.cgi?id=144184=edit apitrace from failed run (mesa git without revert) -- You are receiving this mail because: You are the

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 --- Comment #1 from Ian Romanick --- Is it possible to get a backtrace from __glXSendError? I don't understand why this particular commit would change behavior from "not error" to "error". -- You are receiving this mail because: You are the

[Mesa-dev] [Bug 110632] "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit

2019-05-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110632 Bug ID: 110632 Summary: "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit Product: Mesa Version: git Hardware: x86 (IA32)