[email protected] writes: > Status: Accepted > Owner: ---- > Labels: Type-Maintainability > > New issue 2082 by [email protected]: patchy should check for > guile memory leaks > http://code.google.com/p/lilypond/issues/detail?id=2082 > > apparently there's some way to check for memory leaks in guile? David > wrote: >> In my opinion, Patchy should use -ddebug-gc-assert-parsed-dead by >> default. Apparently the dirt is already in current master (and should >> be bisected and the culprit reverted), but it is definitely a bad idea >> to omit this test when autochecking. > > unfortunately configure doesn't support that option, so I gather that > some kind of work needs to be done on the build system.
Huh? That's on option for _running_ Lilypond, not configuring it. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
