2 This documents serious bugs
4 Send bug reports to bug-gnu-music@gnu.org. For help and questions use
5 help-gnu-music@gnu.org and gnu-music-discuss@gnu.org. Please consult
6 the faq before mailing your problems.
10 [LinuxPPC-R5, egcs-1.1.2-12c]
12 Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:
16 Bug report filed, fixed in egcs-1.1.2-12f or gcc-2.95-0a.
17 Although we've currently got a workaround in place, the compiler
18 is buggy; you should upgrade:
20 ftp://dev.linuxppc.org/users/fsirl/R5/RPMS/ppc/
23 [LinuxPPC-R4, egcs-1.0.2]
25 All compiling with -O2 is suspect, in particular guile-1.3, and
26 Lily herself will break.
31 Lilypond 1.1.35-1.1.51,...: Wierd errors in guile scm_gc_mark ()
36 Some bugs may be captured in input/bugs/*y
38 [Linux i386, RedHat 5.2 with updates to 6.0]
42 configure --disable-checking --enable-printing --disable-optimise --disable-debugging
44 results in core dumps, during parsing of init files. Cause unknown.
47 --enable-checking and --enable-optimize
51 LilyPond occasionally crashes while parsing the initialisation files.
52 This is a very obscure bug, and usually entering the commandline
53 differently "fixes" it.
59 lilypond -I. ./input.ly
66 __libc_malloc (bytes=16384)
68 yyFlexLexer::yy_create_buffer ()
69 Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
72 This behaviour has been observed with machines that have old libg++
73 versions (LinuxPPC feb '98, RedHat 4.x).
79 A problem resembling the previous: usage of libg++.2.8.x with the
80 wrong version of libc results in a coredump from the scanner while
81 reading the init files. Stacktrace:
85 yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
86 yyFlexLexer::yy_get_next_buffer (this=0x8294848)
87 My_lily_lexer::yylex (this=0x8294848)
89 Fix: follow the install instructions of libg++: match the right