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

[Julian S. <js...@ac...>]

Have a look at the function "is_systemish_library_name" in
coregrind/m_debuginfo/readmacho.c.  This causes V not to try to run
dsymutil in various system directories (it's obvious if you look
at the code).  Maybe the path to your Python installation is not
covered by the tests in this function?  LMK if it needs to be
changed.  (or if this does not help).

J

On Friday 22 May 2009, Luc Bourhis wrote:
> 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