https://bugs.freedesktop.org/show_bug.cgi?id=93577
--- Comment #2 from Jose Fonseca <jfons...@vmware.com> ---
(In reply to Michel Dänzer from comment #1)
> Reassigning to Mesa core since it happens with the i965 driver as well, but
> it looks like it might be a game bug.
>
> BTW, an apitrace is only useful if replaying it reproduces the problem.
Actually the apitrace shows the problem:
2347 glXCreateContextAttribsARB(dpy = 0x6c00ec0, config = 0x6d081a0,
share_context = NULL, direct = True, attrib_list =
{GLX_CONTEXT_MAJOR_VERSION_ARB, 4, GLX_CONTEXT_MINOR_VERSION_ARB, 3,
GLX_CONTEXT_PROFILE_MASK_ARB, GLX_CONTEXT_CORE_PROFILE_BIT_ARB, 0}) = NULL
2348 glXMakeCurrent(dpy = 0x6c00ec0, drawable = 0, ctx = NULL) = True
2350 glGenTextures(n = 1, textures = &0)
...
2595 glMapBufferRange(target = GL_PIXEL_PACK_BUFFER, offset = 0, length = 0,
access = GL_MAP_WRITE_BIT | GL_MAP_INVALIDATE_BUFFER_BIT |
GL_MAP_FLUSH_EXPLICIT_BIT) = NULL
The game requests a 4.3 context, it doesn't get one, but happily proceeds using
a null context as if nothing happened ... until it gets a NULL glMapBufferRange
and segfaults.
glretrace skips gl calls with a NULL context (because on Windows the
OPENGL32.DLL silently drops them so quite a few Windows apps inadvertebntly do
it when shutting, so glretrace needs to ignore when replaying on Linux to
prevent crashes)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
