From: Keith W. <ke...@tu...> - 2003-02-04 22:50:11
|
Yes, it seems to segfault while trying to deal with the error returned from the X server. It's correct that there should be an error, but it's not clear why the segfault occurs... Keith Leif Delgass wrote: > It was with the texobj Mesa demo, which appears to call > glDeleteTextures and then glutDestroyWindow on ESC. I haven't looked at > the implementation of glutDestroyWindow yet. > > On Tue, 4 Feb 2003, Keith Whitwell wrote: > > >>>Yes, I ran into this too when the DMA buffer is flushed in >>>radeonDestroyContext. I had tracked it down to the DRI_VALIDATE_DRAWABLE >>>macro in the lock function, so that makes sense. Where is the drawable >>>destroyed? >> >>That's the one. I haven't looked at it deeply yet (which app did you see this >>with?). I assume it gets destroyed in a previous call to XDestroyWindow(), >>which the dri doesn't know anything about. >> >>Keith >> >> > > |