release: 1.0.17

[lilypond.git] / BUGS

diff --git a/BUGS b/BUGS
index 6c32757d6a7a3312b2eb868cd42523eb316237c0..054d425246941e3b94db75c303ab66b7b7458f03 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1,33 +1,45 @@
-Document Really Ugly Bugs (coredumps, assert fails, etc)
 
+This documents serious bugs 
 
-\score{
-       \melodic{
-       [a8 a-2] /bla
+********
+
+[Linux Intel, EGCS-1.1b]
+
+Compiling with -O2 -finline-functions will cause crashes during
+parsing stage.
+
+
+[All platforms] 
+
+When dealing with beaming that is not correct (eg quarter notes in
+beams.), you can get the following assert.  This is a serious bug, but
+a good solution is quite a lot of work.
+
+       \score{
+               \melodic{
+                       [c2 c]
+               }
        }
-}
-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)
 
+results in
+
+       lilypond: ../flower/include/varray.hh:141: struct Rhythmic_grouping *& Array<Rhythmic_grouping *>::elem(int) const: Assertion `i >=0&&i<size_' failed.
 
-[GNU libc]
+And this
 
-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.
+       \score{
+               \melodic{
+                       [c]
+               }
+       }
 
+in
 
-[IRIX (5.3?)]
+       lilypond: ../flower/include/cursor.tcc:104: int Cursor<void *>::operator -(class Cursor<void *>) const: Assertion `c.ok()' failed.
+       Aborted (core dumped)
 
-coredump from strstream::strstream () upon the first read of a file
 
-[Linux Intel]
+[Linux libg++ 2.7]
 
 LilyPond occasionally crashes while parsing the initialisation files.
 This is a very obscure bug, and usually entering the commandline
@@ -50,11 +62,9 @@ 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]