It's a little unfortunate that the author did not at least try to hunt down a few of them and present a conlclusion about if the warnings are benign or serious.

It's a little unfortunate that the author did not at least try to hunt down a few of them and present a conlclusion about if the warnings are benign or serious. I don't have the exact version of Mesa that the blog-post (http://www.americanteeth.org/2013/08/14/valgrind-is-not-optional/ http://www.americanteeth.org/2013/08/14/valgrind-is-not-opti...) seems to refer to. But the first two functions in the i965 driver code that valgrind complained about basically do something like the following code: uint32_t *surf = brw_state_batch(...) surf[0] = ...stuff with flags for the GPU-code... (...) surf[5] = ...even more stuff, encoding coordinates and so on... (...) Unfortunately that pointer "*surf" seems to be allocated by some batch-buffer-memory allocation magic, so (after only greping through the source for 5 minutes) I would not be able to conclude if it's a fake warning (maybe refering to some memory that is allocated by some DRI kernel interface mmap-magic) or indeed serious (say, a mistake when calculating the proper boundaries of allocated pages). But with a library used as regularly as Mesa I'd give the authors the benefit of doubt and guess that to detect the subtle errors, one would first have to educate valgrind about that DRI-specific way of allocating memory.