This is a mad-hack, but I am trying to deliberately cause a segfault at a particular point in execution, so valgrind will give me a stack trace.
Valgrind tells me function xxx allocated memory which was not freed. Fine. It\'s proving more difficult than usual to trace however.
I\'ve tried to debug memory crash in开发者_运维问答 my Python C extension and tried to run script under valgrind. I found there is too much \"noise\" in the valgrind output, even if I\'ve ran simple c