Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel

[lilypond]

Comment #2 on issue 1096 by v.villenave: ly:parser-parse-string segfaults  
when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096

I didn't mark it as High because in no circumstance it would affect someone  
who uses
LilyPond in a "normal" (i.e. non-geeky, non-hackish) way.
I (and Nicolas, and Michael, and probably a few others) really need this to  
be
addressed (hence the bounty), but I don't think it should block a release.  
Especially
since it doesn't always prevent the PDF from being generated (er, sometimes  
it does,
actually).