<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110632#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - "glx: Fix synthetic error generation in __glXSendError" broke wine games on 32-bit"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110632">bug 110632</a>
from <span class="vcard"><a class="email" href="mailto:Hi-Angel@yandex.ru" title="Hi-Angel <Hi-Angel@yandex.ru>"> <span class="fn">Hi-Angel</span></a>
</span></b>
<pre>(In reply to Ian Romanick from <a href="show_bug.cgi?id=110632#c1">comment #1</a>)
<span class="quote">> 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".</span >
Sure, can you tell offhand though, in which line can I set an "abort()" to
cause a core dump on the error?
I tried to get a stacktrace both from gdb and winedbg, but for various reasons
neither works.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>