Am 26.07.16 um 17:09 schrieb sth:
it's difficult to test a .dylib / .so using valgrind
Why is it difficult? If you have a python script such that
python mytests.py
loads the .so and runs the tests, then
valgrind --tool=memcheck python mytests.py
should work. This should immediately spit out an error in case that
numpy accesses deleted memory.
Of course debug information should be enabled when compiling the .so for
more useful output, and it could be helpful to have it for numpy/python,
too, but that's not a requirement.
Christian
--
https://mail.python.org/mailman/listinfo/python-list
