Re: Issue 2082 in lilypond: patchy should check for guile memory leaks

[lilypond]

Comment #3 on issue 2082 by address@hidden: patchy should check  
for guile memory leaks
http://code.google.com/p/lilypond/issues/detail?id=2082

yes, so evidently we'd need an
  --enable-guile-memory-check
flag for configure, which would set a flag in the build system,
which would add that -ddebug-gc-assert-parsed-dead to lilypond
calls within the regtest compiling.

I think that's the overall sketch of the solution.  It'd probably
take me 30 minutes to get this added; call it 60 minutes for
lilypond developers who joined after me, and 15 minutes for people
who were here before me?