[Bug 92749] seg fault in glTexImage2D
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Oct 30 17:54:18 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=92749
--- Comment #7 from Ian Romanick <idr at freedesktop.org> ---
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20151031/c6faf717/attachment.html>
More information about the intel-3d-bugs
mailing list