release: 1.2.7

[lilypond.git] / BUGS

diff --git a/BUGS b/BUGS
index 5f4755d57ab50a8f424d8221e83c74b7715ea35b..8fb51c7c21fa12ffe0da9e401c21949f834abb86 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1,43 +1,64 @@
-Document Really Ugly Bugs (coredumps, assert fails, etc)
 
+This documents serious bugs 
 
-\score{
-       \melodic{
-       [a8 a-2] /bla
-       }
-}
-koor.ly: 4: error: parse error, expecting `DIGIT' or `UNSIGNED':
-        [a8 a-2] /bla
-                     
-koor.ly: 5: error: Have to be in Lyric mode for lyrics:
-        }
-         
-lilypond: parser.y:765: int yyparse(void *): Assertion `((My_lily_parser *) my_lily_parser_l)->post_reqs.empty ()' failed.
-Aborted (core dumped)
+Send bug reports to bug-gnu-music@gnu.org.  For help and questions use
+help-gnu-music@gnu.org and gnu-music-discuss@gnu.org.  Please consult
+the faq before mailing your problems.
 
 
-[gcc 2.8.x/libstdc++ 2.8.x/libg++ 2.8.0]
 
-The latest gcc release causes lily to crash just after Interpreting
-music:
+********
 
-stacktrace looks something like:
+[LinuxPPC-R5, egcs-1.1.2-12c]
 
-      __DTOR_END__ ()
-      __malloc ()
+Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:
 
-[GNU libc]
+       *dest++ = *src++;
 
-The GNU extension memmem() is known to be buggy on linux libc 5.0.9
-and before. Glibc upto 2.0.5 also has problems with memmem (), but
-these should not affect LilyPond.
+Bug report filed, fixed in egcs-1.1.2-12f or gcc-2.95-0a.
+Although we've currently got a workaround in place, the compiler
+is buggy; you should upgrade:
 
+       ftp://dev.linuxppc.org/users/fsirl/R5/RPMS/ppc/ 
 
-[IRIX (5.3?)]
 
-coredump from strstream::strstream () upon the first read of a file
+[LinuxPPC-R4, egcs-1.0.2]
 
-[Linux Intel]
+All compiling with -O2 is suspect, in particular guile-1.3, and
+Lily herself will break.
+
+
+[Linux i386]
+
+A binary RPM of Guile 1.3 has been distributed from the LilyPond ftp
+site.  This binary was made in RedHat 5.x, and it will fail if this
+RPM is used with RedHat 6.x.
+
+[GUILE 1.3.2]
+
+Guile 1.3.2 is buggy in several respects. Do not use it for LilyPond.
+
+[LinuxPPC, egcs-1.1b]
+
+Lilypond 1.1.35-1.1.51,...:  Wierd errors in guile scm_gc_mark ()
+
+
+[All platforms] 
+
+Some bugs may be captured in input/bugs/*y
+
+[Linux i386, RedHat 5.2 with updates to 6.0]
+
+Compiling with 
+
+       configure --disable-checking --enable-printing --disable-optimise --disable-debugging
+
+results in core dumps, during parsing of init files. Cause unknown.
+Solution: use
+
+       --enable-checking and --enable-optimize
+
+[Linux libg++ 2.7]
 
 LilyPond occasionally crashes while parsing the initialisation files.
 This is a very obscure bug, and usually entering the commandline
@@ -60,24 +81,7 @@ Typical stacktrace:
        Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
                :
 
+This behaviour has been observed with machines that have old libg++
+versions (LinuxPPC feb '98, RedHat 4.x).  
 
-I get bitten by this every once in a while, and I am very interested
-in hints what might be wrong.  This problem has only been identified
-with libc-5.3 and libc-5.4 platforms, so you might try upgrading to
-6.0, ie. GNU libc-2.
-
-
-[Linux Intel]
-
-A problem resembling the previous: usage of libg++.2.8.x with the
-wrong version of libc results in a coredump from the scanner while
-reading the init files.  Stacktrace:
-
-       ios::eof (this=0x0)
-       
-       yyFlexLexer::LexerInput (this=0x8294848, buf=0x82955f0 "", max_size=8192)
-       yyFlexLexer::yy_get_next_buffer (this=0x8294848)
-       My_lily_lexer::yylex (this=0x8294848) 
 
-Fix: follow the install instructions of libg++: match the right
-library versions.