1 Document Really Ugly Bugs (coredumps, assert fails, etc)
9 koor.ly: 4: error: parse error, expecting `DIGIT' or `UNSIGNED':
12 koor.ly: 5: error: Have to be in Lyric mode for lyrics:
15 lilypond: parser.y:765: int yyparse(void *): Assertion `((My_lily_parser *) my_lily_parser_l)->post_reqs.empty ()' failed.
19 [gcc 2.8.x/libstdc++ 2.8.x/libg++ 2.8.0]
21 The latest gcc release causes lily to crash just after Interpreting
24 stacktrace looks something like:
31 The GNU extension memmem() is known to be buggy on linux libc 5.0.9
32 and before. Glibc upto 2.0.5 also has problems with memmem (), but
33 these should not affect LilyPond.
38 coredump from strstream::strstream () upon the first read of a file
42 LilyPond occasionally crashes while parsing the initialisation files.
43 This is a very obscure bug, and usually entering the commandline
44 differently "fixes" it.
50 lilypond -I. ./input.ly
57 __libc_malloc (bytes=16384)
59 yyFlexLexer::yy_create_buffer ()
60 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
64 I get bitten by this every once in a while, and I am very interested
65 in hints what might be wrong. This problem has only been identified
66 with libc-5.3 and libc-5.4 platforms, so you might try upgrading to
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