<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - seg fault in glTexImage2D"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92749#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - seg fault in glTexImage2D"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92749">bug 92749</a>
from <span class="vcard"><a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> <span class="fn">Ian Romanick</span></a>
</span></b>
<pre>Sorry... I didn't ask clearly enough. I just wanted a stack backtrace from GDB
from the point of the segfault. You should just be able to
gdb --args ./glretrace seg_fault_glTexImage2d.trace
"r", the "bt".
There are a couple weird things in that trace... are you really setting the
filter mode and warp modes with glTexParameterf (instead of glTexParameteri)?
It's legal, but a little weird...
I wonder if the segfault (which only occurs for you in apitrace, right?) is due
to apitrace doing weird things with GL_UNPACK_* settings you're using... like
not having the source buffer set up correctly so that glTexImage reads past the
end or something. Dunno.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>