----- Original Message ----- > The only nearly robust way to solve this issue is Brian Paul's > suggestion. > If spawning a separate process to run the test is too expensive, > install a > signal/exception handler around your GLX initialization and tests. > That way > you can detect crashes AND actually use the resulting context if it > passes > your tests.
Yes, I'm going to follow Brian's suggestion and run the driver detection in a separate process. But no, installing a signal handler is not going to work for me, because if a segfault is related to memory corruption, I would rather not silence it and continue. Benoit _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
