I intend to look into this problem, probably over the weekend. I've got at least one test program of my own to exercise this. Agreed, we shouldn't crash.
-Brian Jens Owen wrote: > Brian, do these tests look reasonable to you? We certainly shouldn't > crash the server, even if they are unreasonable. > > Joe, can your try with the DRI CVS trunk? > > Joe Krahn wrote: > >>I am trying to draw to two windows using one context. >>It works for Mesa, but gives severe artifacts with DRI. >>It would work to instead use glXCopyContext, but this >>still doesn't work for DRI, and it crashes the server >>with indirect rendering. >> >>I am using ATI Rage and Radeon, with XFree86 CVS. >>Haven't tried DRI CVS yet, but I will do this soon. >> >>Here is a test app illustrating context bugs: >>http://home.nc.rr.com/krahnfamily/source/cxbug.c >>Aside from fixing bugs, any ideas on a workaround >>to share a context in DRI? >> >>Another unrelated thing, not actually DRI: glDrawPixels >>with GL_BITMAP and an incorrect format correctly gives an >>error in DRI, but indirect results in an Xlib error: >>http://home.nc.rr.com/krahnfamily/source/bitmap_bug.c >> >>Thanks, >>Joe Krahn _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
