2 This documents serious bugs
6 [Linux ppc, egcs-1.0.2]
8 All compiling with -O2 is suspect, in particular guile-1.3, and
9 Lily herself will break.
14 When dealing with beaming that is not correct (eg quarter notes in
15 beams.), you can get the following assert. This is a serious bug, but
16 a good solution is quite a lot of work.
26 lilypond: ../flower/include/varray.hh:141: struct Rhythmic_grouping *& Array<Rhythmic_grouping *>::elem(int) const: Assertion `i >=0&&i<size_' failed.
38 lilypond: ../flower/include/cursor.tcc:104: int Cursor<void *>::operator -(class Cursor<void *>) const: Assertion `c.ok()' failed.
44 LilyPond occasionally crashes while parsing the initialisation files.
45 This is a very obscure bug, and usually entering the commandline
46 differently "fixes" it.
52 lilypond -I. ./input.ly
59 __libc_malloc (bytes=16384)
61 yyFlexLexer::yy_create_buffer ()
62 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
65 This behaviour has been observed with machines that have old libg++
66 versions (LinuxPPC feb '98, RedHat 4.x).
72 A problem resembling the previous: usage of libg++.2.8.x with the
73 wrong version of libc results in a coredump from the scanner while
74 reading the init files. Stacktrace:
78 yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
79 yyFlexLexer::yy_get_next_buffer (this=0x8294848)
80 My_lily_lexer::yylex (this=0x8294848)
82 Fix: follow the install instructions of libg++: match the right