Your message dated Sun, 28 Jan 2007 10:29:30 -0600
with message-id <[email protected]>
has caused the Debian Bug report #384518,
regarding libgl1-mesa-glx: crashes R-cran-rgl when exporting to pdf
to be marked as having been forwarded to the upstream software
author(s) Daniel Adler <[email protected]>, Duncan Murdoch
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Re: X11 protocol errors
Sun, 28 Jan 2007 10:29:30 -0600
Ok, thanks, I am passing this through to the rgl upstream authors.
This is the issue that was raised recently and which is logged at
and I hope you are in a better position than I am to comment on this.
As we noticed, the outright segfault appears to be fixed in 0.70, but Michel
sees some discrepancies with respect to the GLX specs.
Best regards, Dirk
On 23 January 2007 at 18:25, Michel Dänzer wrote:
| reassign 384518 r-cran-rgl
| reassign 357439 libwxgtk2.6-0
| Looks like I still didn't look at these errors closely enough... :}
| Looking at the function DoMakeCurrent() in the xorg-server file
| glxcmds.c, it only returns BadMatch or GLXBadContextState under two
| conditions, which are stated explicitly in the GLX spec:
| 'GLXBadContextState is generated if there is a current rendering
| context and its render mode is either GL FEEDBACK or GL SELECT.'
| (So the problem is that the *previously bound* context has
| render mode != GL_RENDER, not the newly bound one)
| 'If ctx is NULL and draw is not None, or if draw is None and ctx
| is not NULL, then a BadMatch error will be generated.'
| So it would appear that these errors are caused by bugs not in the GLX
| implementation but in the components which call glXMakeCurrent, and I'm
| reassigning them back. Of course, it's possible that these errors
| originate from DoMakeCurrent()'s calls to GetDrawableOrPixmap() or
| __glXForceCurrent() or are otherwise caused by circumstances which
| aren't the fault of these components. If you suspect so, please trace
| the DoMakeCurrent() function with gdb or debugging output to find out
| why it generates these errors.
| Apologies for not realizing this earlier, I hope this is still useful.
| Earthling Michel Dänzer | http://tungstengraphics.com
| Libre software enthusiast | Debian, X and DRI developer
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--- End Message ---