On 08/04/2010 05:58 PM, tom fogal wrote: > > If you can find the commit that started the trouble (using git bisect), > that might shed some light. >
I ran :
git bisect start
git bisect bad
git bisect good mesa_7_6
git bisect run ~/kitware/os_bisect_script.sh
The os_bisect_script.sh script is attached.
Git bisect reported :
36b3a8bd5a317ab297f44b19fd14c7e76ec2fc77 is the first bad commit
commit 36b3a8bd5a317ab297f44b19fd14c7e76ec2fc77
Author: Brian Paul <bri...@vmware.com>
Date: Tue May 4 21:44:02 2010 -0600
osmesa: fix OSMesa for CHAN_BITS=32
CHAN_BITS=16 still broken.
NOTE: this is a candidate for back-porting to the 7.8 stable branch.
:040000 040000 0f65d1684966e414854f91dd3dbf4c80afe2af8d
4e47ee7d7f77ce5726446422ea45e1a4cf3083e2 M src
bisect run success
This seems to be where the test started failing but it didn't start
segfaulting here.
I'll adjust my script to search for that.
os_bisect_script.sh
Description: application/shellscript
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
