release: 1.1.1

[lilypond.git] / BUGS

diff --git a/BUGS b/BUGS
index f7da705fa8b60c598cce7c13bb5d0bd96db3dbd6..1651e800d6de2645b96bb1c12d9c065dc7031491 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1,32 +1,51 @@
-input/abbrev.ly
+
+This documents serious bugs 
 
 ********
-\score{
-       \melodic{
-               [c2 c]
-       }
-}
-lilypond: ../flower/include/varray.hh:141: struct Rhythmic_grouping *& Array<Rhythmic_grouping *>::elem(int) const: Assertion `i >=0&&i<size_' failed.
-Aborted (core dumped)
-*********
-\score{
-       \melodic{
-               [c]
+
+[Linux Intel, EGCS-1.1b]
+
+Compiling with -O2 -finline-functions will cause crashes during
+parsing stage.
+
+
+[Linux ppc, egcs-1.0.2]
+
+All compiling with -O2 is suspect, in particular guile-1.3, and
+Lily herself will break.
+
+
+[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]
+               }
        }
-}
-lilypond: ../flower/include/cursor.tcc:104: int Cursor<void *>::operator -(class Cursor<void *>) const: Assertion `c.ok()' 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
 
-[Linux Intel]
+       lilypond: ../flower/include/cursor.tcc:104: int Cursor<void *>::operator -(class Cursor<void *>) const: Assertion `c.ok()' failed.
+       Aborted (core dumped)
+
+
+[Linux libg++ 2.7]
 
 LilyPond occasionally crashes while parsing the initialisation files.
 This is a very obscure bug, and usually entering the commandline
@@ -49,11 +68,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]