On Fri, Apr 18, 2014 at 5:30 PM, Ian Romanick <i...@freedesktop.org> wrote: > On 04/18/2014 05:07 PM, Jamey Sharp wrote: >> if you're using Xlib, then by default it will be abort()ing your >> client as soon as it pulls the error out of the event queue. > > Unless the client has an error handler, right?
Well, sure, the usual horrid Xlib error handling rules apply: Mesa could install an async_handler to filter its errors, and the application could call XSetErrorHandler. But the former seems silly when you already had to check for a null reply pointer, and requiring callers to both set an X error handler and check the return values from their libGL calls seems silly too. Now that you've had a refresher after three years, does this make more sense? :-) Jamey _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev