Valgrinding lilypond for a stack trace

[Mike Solomon]

Hey all,

I am doing some devel on lilypond and I'm getting a persistent Scheme error at 
a certain point.  Before I insert a litany of pretty-prints to figure out where 
this is happening, is there a way to valgrind lilypond so that it dumps all 
functions called into a file in linear order?  I'd then skim this file to 
figure out when lily died & why.

Cheers,
MS