Issue 380 in lilypond: cycling markup reference segfaults

[codesite-noreply]

Issue 380: cycling markup reference segfaults
http://code.google.com/p/lilypond/issues/detail?id=380

Comment #5 by gpermus:
Hmm... in that case, we simply let the user crash his system?  ;)

If nobody has any brilliant ideas about this bug, shall I mark it closed?  
Perhaps
add a sentence somewhere in the docs to warn users that they can crash lilypond 
if
they use cyclic references in markup?



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings