summaryrefslogtreecommitdiff
path: root/scripts/valgrind.sup
Commit message (Collapse)AuthorAgeFilesLines
* [core] Make sure ThreadLocal will not own the pointer it is managingThiago Marcos P. Santos2017-07-141-8/+0
| | | | | | | | | | | | | | ThreadLocal should not own the pointer it is managing because the use case in Mapbox GL is to keep a pointer to a stack allocated object, like: ``` MyObject foo; threadLocal.set(&foo); ``` To keep consistency, it is required that we clear the managed object before ThreadLocal gets destroyed by setting it to `nullptr`.
* [build] upgrade to v4 CircleCI images that have logbt/mesa/gdb/apitrace ↵Konstantin Käfer2017-07-131-279/+17
| | | | installed
* [build] Updated valgrind suppressionsBruno de Oliveira Abinader2017-06-221-0/+9
|
* [linux] mesa 13.0.3John Firebaugh2017-01-231-0/+71
|
* [build] Use mesa-13.0.0-glx in CI buildsBruno de Oliveira Abinader2016-11-081-0/+86
|
* [Qt][build] Updated valgrind supression and make it a target for QtThiago Marcos P. Santos2016-06-091-34/+125
|
* Add a reference Valgrind suppresion fileThiago Marcos P. Santos2015-03-201-0/+91
When using Valgrind for debugging memory leaks and access violations, we often see a lot of false positives, specially when dealing with OpenGL that does it own buffer management. This file is an attempt to filter these false positives. Note that we are only filtering for the open source Radeon driver and the list will probably grow to accommodate other setups. To use the Valgrind with the suppression file for hunting memory leaks, try something like: valgrind --leak-check=full --track-origins=yes --suppressions=[path/to/valgrind.sup] ./mapbox-gl