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.
21 The GNU extension memmem() is known to be buggy on linux libc 5.0.9
22 and before. Glibc upto 2.0.5 also has problems with memmem (), but
23 these should not affect LilyPond.
28 coredump from strstream::strstream () upon the first read of a file
32 LilyPond occasionally crashes while parsing the initialisation files.
33 This is a very obscure bug, and usually entering the commandline
34 differently "fixes" it.
40 lilypond -I. ./input.ly
47 __libc_malloc (bytes=16384)
49 yyFlexLexer::yy_create_buffer ()
50 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
54 I get bitten by this every once in a while, and I am very interested
55 in hints what might be wrong. This problem has only been identified
56 with libc-5.3 and libc-5.4 platforms, so you might try upgrading to
62 A problem resembling the previous: usage of libg++.2.8.x with the
63 wrong version of libc results in a coredump from the scanner while
64 reading the init files. Stacktrace:
68 yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
69 yyFlexLexer::yy_get_next_buffer (this=0x8294848)
70 My_lily_lexer::yylex (this=0x8294848)
72 Fix: follow the install instructions of libg++: match the right