2 This documents serious bugs
9 When dealing with beaming that is not correct (eg quarter notes in
10 beams.), you can get the following assert. This is a serious bug, but
11 a good solution is quite a lot of work.
21 lilypond: ../flower/include/varray.hh:141: struct Rhythmic_grouping *& Array<Rhythmic_grouping *>::elem(int) const: Assertion `i >=0&&i<size_' failed.
33 lilypond: ../flower/include/cursor.tcc:104: int Cursor<void *>::operator -(class Cursor<void *>) const: Assertion `c.ok()' failed.
39 LilyPond occasionally crashes while parsing the initialisation files.
40 This is a very obscure bug, and usually entering the commandline
41 differently "fixes" it.
47 lilypond -I. ./input.ly
54 __libc_malloc (bytes=16384)
56 yyFlexLexer::yy_create_buffer ()
57 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
60 This behaviour has been observed with machines that have old libg++
61 versions (LinuxPPC feb '98, RedHat 4.x).
67 A problem resembling the previous: usage of libg++.2.8.x with the
68 wrong version of libc results in a coredump from the scanner while
69 reading the init files. Stacktrace:
73 yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
74 yyFlexLexer::yy_get_next_buffer (this=0x8294848)
75 My_lily_lexer::yylex (this=0x8294848)
77 Fix: follow the install instructions of libg++: match the right