I have a process that is called by another process which is called by another process and so on ad nauseum. It\'s a child process in a long tool chain.
This process
Not exactly what you expect, but it might help you in debugging.
valgrind --trace-children=yes your_program
will check and print memory errors in all children of the process, with stack trace and some detail about the error (eg. in case of double-free, you'd get the stack trace of the first free).
Also, you might make the crashing process generate a core dump, and debug this post-mortem. See this answer for details.