[Mesa-dev] segfault in pstip_bind_sampler_states

Brian Paul brianp at vmware.com
Tue Aug 13 06:50:10 PDT 2013


On 08/12/2013 11:30 AM, Kevin H. Hobbs wrote:
> On 08/12/2013 10:29 AM, Brian Paul wrote:
>> Can you run with valgrind?  That should give us some useful info if
>> there's a use-after-free.
>
> Sure,
>
> $ valgrind /home/kevin/kitware/VTK_OSMesa_Build/bin/vtkpython
> "--enable-bt"
> "/home/kevin/kitware/VTK_OSMesa_Build/Utilities/vtkTclTest2Py/rtImageTest.py"
> "/home/kevin/kitware/VTK/Filters/Hybrid/Testing/Python/largeImageOffset.py"
> "-D" "/home/kevin/kitware/VTK_OSMesa_Build/ExternalData/Testing" "-T"
> "/home/kevin/kitware/VTK_OSMesa_Build/Testing/Temporary" "-V"
> "/home/kevin/kitware/VTK_OSMesa_Build/ExternalData/Filters/Hybrid/Testing/Data/Baseline/largeImageOffset.png"
> "-A" "/home/kevin/kitware/VTK_OSMesa_Build/Utilities/vtkTclTest2Py" >
> /tmp/osmesa_valgrind.txt 2>&1
>

[...]

> ==30166==
> --30166-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
> --30166-- si_code=80;  Faulting address: 0x0;  sp: 0x4030fdd50
>
> valgrind: the 'impossible' happened:
>    Killed by fatal signal

Well, that's not too helpful.  Can you send me an executable?  Or, is it 
simple to build the test case?

-Brian



More information about the mesa-dev mailing list