https://bugs.freedesktop.org/show_bug.cgi?id=81500
--- Comment #23 from Barto <mister.free...@laposte.net> --- (In reply to comment #22) > From what I can see, this commit has nothing to do with any issues > introduced by the originally bad commit... this will require some > investigation. > > Summary: > > apitrace: > http://demo.ovh.eu/download/365b2f85df30b16ec7539d7b9622542a/fgfs.tar.bz2 > > first bad commit: d030a3404ca0fedf365cb0fd41eaad7abc8ff132 > commit that "fixes" it on master: 1d9f74eda75da05b4d5c7df5fc1e6f5ab8d88322 yes it's strange, it seems that this commit can cancel the bugs made by the bad commit d030a3404ca0fedf365cb0fd41eaad7abc8ff132, I don't know how, I could use gdb with breakpoints but my knowledge in opengl programming is too weak, anyway this commit 1d9f74eda75da05b4d5c7df5fc1e6f5ab8d88322 solves the problem, but I will understand if you think it's too dangerous to use this commit in 10.2 branch of mesa -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
