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

[lilypond]

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

The problem is that the embedded scm causes a recursive yyparse() to be  
invokved.
However, when the string input is parsed, the parser does not return to the  
outer
scope, hence the syntax error. The segfault occurs when the Flex buffers are
deallocated and control finally returns to the originally yyparse and  
segfaults.

I've attached a patch for this issue that leaves nested yyparses when  
needed.

Attachments:
        0001-fix-ly-parser-parse-file-in-an-ly-file.patch  4.7 KB