Updates:
Status: Verified
Comment #7 on issue 716 by v.villenave: --disable-optimising causes `Parsed
object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
(No comment was entered for this change.)
--
You received this message because you are listed in the own
Updates:
Status: Fixed
Labels: fixed_2_12_3
Comment #6 on issue 716 by n.puttock: --disable-optimising causes `Parsed
object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
(No comment was entered for this change.)
--
You received this message because y
Updates:
Status: Verified
Comment #5 on issue 716 by v.villenave: --disable-optimising causes `Parsed
object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
(No comment was entered for this change.)
--
You received this message because you are listed in the own
Updates:
Status: Fixed
Labels: fixed_2_13_2
Comment #4 on issue 716 by joeneeman: --disable-optimising causes `Parsed
object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
I did, but I couldn't find the bug report. Thanks.
--
You received this message
Comment #3 on issue 716 by n.puttock: --disable-optimising causes `Parsed
object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
Looks like Joe has fixed this with commit
5ea3f07e4d8a70a37d00e25b87db60cd50f4e06c.
--
You received this message because you are listed i
Updates:
Summary: --disable-optimising causes `Parsed object should be dead'
Comment #2 on issue 716 by nicolas.sceaux: --disable-optimising causes
`Parsed object should be dead'
http://code.google.com/p/lilypond/issues/detail?id=716
The problem was indeed introduced by commit
b6c67
