There was a subtle behaviour change to the (undefined) results of using strcpy() and memcpy() on overlapping memory regions that could lead to curious issues like this. Is it possible your code is buggy in such a way? Given that I've gotten no other reports of the newer glibc breaking OpenGL, this is all I can think of off the top of my head.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072384 Title: Update to libc6 causes OpenGL to function erractly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1072384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
