[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly
From: |
lilypond |
Subject: |
Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel |
Date: |
Fri, 21 May 2010 11:01:29 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium Syntax Bounty
New 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
%% The following code exits with a segfault, even though the
%% PDF is still generated.
\version "2.13.21" % never worked AFAWK
#(ly:parser-parse-string parser "{ g }")
%% This also reproduces the bug:
%#(ly:parser-parse-string parser "\\include \"italiano.ly\"")
%{ do' }
% You may also want to look at the discussion on
http://lists.gnu.org/archive/html/lilypond-devel/2010-02/msg00106.html
As always, I'm willing to throw in €50, or double another offer (within
reasonable limits, that is ;) to whoever fixes this in an acceptable way.
- Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel,
lilypond <=
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/21
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/23
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/26
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/27
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/27
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/27
- Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 2010/05/30