From: fred <fred>
Date: Sun, 24 Mar 2002 20:10:13 +0000 (+0000)
Subject: lilypond-1.0.1
X-Git-Tag: release/1.5.59~3180
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=5992d8b0e4c16649a14a32bbfeaaaf0d99b9a56e;p=lilypond.git

lilypond-1.0.1
---

diff --git a/BUGS b/BUGS
index f7da705fa8..36b24a234a 100644
--- a/BUGS
+++ b/BUGS
@@ -1,32 +1,40 @@
-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]
+
+
+[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 +57,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]