[Valgrind-users] More selective --auto-run-dsymutil

[Luc B. <luc...@ma...>]

Hello there,

I am developing Python extensions (in C++, using Boost.Python but it  
does not matter). I run all my Python test cases through valgrind,

	valgrind --auto-run-dsymutil python foo.py

so as to catch bugs in those Python extensions. The problem is that  
valgrind wants to run dsymutil not only on my Python extensions but  
also on the Python executable and the whole of the standard Python  
library. Those dsymutil calls fail, of course, because valgrind wants  
to write the dSYM directories next to those and since I run valgrind  
as a normal user, it does not have the permission to do that.

Would there be a workaround for that problem? This is quite annoying  
because it produces so much noise…

Luc Bourhis