https://bugs.freedesktop.org/show_bug.cgi?id=54372
Ian Romanick <i...@freedesktop.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |i...@freedesktop.org,
| |jbar...@virtuousgeek.org
--- Comment #11 from Ian Romanick <i...@freedesktop.org> ---
I don't know how I never saw this bug before. Sorry about that. :( I'm also
adding Jesse to the CC list... because git-blame says he wrote all of this
code.
The NULL pointer from GetGLXDrawable is a pretty catastrophic event at this
point in the code. GetGLXDrawable and dri2GetGlxDrawableFromXDrawableId
(earlier in the function) look up the drawable IDs in separate hash tables.
The entry for dri2GetGlxDrawableFromXDrawableId is added in dri2CreateDrawable,
and the entry for GetGLXDrawable is added in InitGLXDrawable. Both of these
functions are called together (see CreateDrawable in glx_pbuffer.c for an
example).
The entries are removed from the hash tables by DestroyGLXDrawable and
DestroyDRIDrawable. These are also called together (see DestroyDrawable in
glx_pbuffer.c).
So... if one hash table has the entry and the other does not, that suggests
that we're between the DestroyGLXDrawable and DestroyDRIDrawable calls... which
seems hella crazy because your backtrace is in the middle of a glXSwapBuffers
call (though perhaps not for the same drawable?).
Assuming you can recreate this crash at will, at the time of the crash:
1. What is the value of awire->drawable?
2. What is the value of pdraw->drawable?
3. In the dri2SwapBuffers frame, what is the value of pdraw? This is just from
the backtrace.
4. In the glXSwapBuffers frame, what is the value of drawable? This is just
from the backtracke.
5. Is your app multithreaded?
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
