[Mesa-dev] [Bug 33758] New: CreateDRIDrawable can't fail gracefully
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jan 31 06:05:34 PST 2011
https://bugs.freedesktop.org/show_bug.cgi?id=33758
Summary: CreateDRIDrawable can't fail gracefully
Product: Mesa
Version: git
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: GLX
AssignedTo: mesa-dev at lists.freedesktop.org
ReportedBy: nobled at dreamwidth.org
(I'm running on Ubuntu 10.04 x86-32 with mesa from the 7.10 Natty package, just
for the record - but this bug is also in git and older versions.)
In src/glx/glx_pbuffer.c, CreateDRIDrawable can fail, in which case it prints
"failed to create drawable", but the caller has no way of knowing that it
failed at all and just keeps going.
Whenever I called eglCreatePbuffer, "failed to create drawable" gets printed
(not sure why - because Ubuntu 10.04 has a slightly older X server?), but I got
a seemingly valid EGLSurface anyway. And when I tried to use it in
eglMakeCurrent(), I get a mysterious segfault:
Breakpoint 4, GLX_eglMakeCurrent (drv=0x80ec2e0, disp=0x80eb680,
dsurf=0x8164370, rsurf=0x8164370, ctx=0x816ed10) at egl_glx.c:738
(gdb) next
(...)
760 ret = GLX_drv->glXMakeCurrent(GLX_dpy->dpy, ddraw, cctx);
(gdb) next
Program received signal SIGSEGV, Segmentation fault.
0x00434e18 in ?? () from /usr/lib/mesa/libGL.so.1
(gdb) bt
#0 0x00434e18 in ?? () from /usr/lib/mesa/libGL.so.1
#1 0x004356a7 in ?? () from /usr/lib/mesa/libGL.so.1
#2 0x004346f2 in ?? () from /usr/lib/mesa/libGL.so.1
#3 0x00412c3f in glXMakeCurrentReadSGI () from /usr/lib/mesa/libGL.so.1
#4 0x00412dd3 in glXMakeCurrent () from /usr/lib/mesa/libGL.so.1
#5 0x00462e8c in GLX_eglMakeCurrent (drv=0x80ec2e0, disp=0x80eb680,
dsurf=0x8164370, rsurf=0x8164370, ctx=0x816ed10) at egl_glx.c:760
#6 0x00454f8f in eglMakeCurrent (dpy=0x80eb680, draw=0x8164370,
read=0x8164370, ctx=0x816ed10) at eglapi.c:478
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the mesa-dev
mailing list