[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 2082 in lilypond: patchy should check for guile memory leaks
|
From: |
lilypond |
|
Subject: |
Re: Issue 2082 in lilypond: patchy should check for guile memory leaks |
|
Date: |
Tue, 06 Dec 2011 02:12:42 +0000 |
Comment #1 on issue 2082 by address@hidden: patchy should check for
guile memory leaks
http://code.google.com/p/lilypond/issues/detail?id=2082
According to outputs from an old regtest
http://code.google.com/p/lilypond/issues/attachmentText?id=36&aid=360005000&name=error-snip&token=c948f6e3f4f39ff49439c2fd2f72d8aa
we can debug garbage collection with
lilypond -ddebug-gc file
So what we'd propose to do is run the regtests with lilypond -ddebug-gc
used in each call to lilypond.
How to actually make that happen, I have no idea.