X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=BUGS;h=5fe9ab69ee795d1ab2b08e43e4cb6330eb621d6a;hb=refs%2Ftags%2Frelease%2F1.1.64;hp=40be3fcf2895f97369cf4522f400cb4e46261e4f;hpb=b1eda2bf8186760c557b770833c172a8979bc538;p=lilypond.git

diff --git a/BUGS b/BUGS
index 40be3fcf28..5fe9ab69ee 100644
--- a/BUGS
+++ b/BUGS
@@ -1,7 +1,48 @@
-Document Really Ugly Bugs (coredumps, assert fails, etc)
 
+This documents serious bugs 
+
+********
+
+[LinuxPPC-R5, egcs-1.1.2-12c]
+
+Serious egcs-1.1.2-12c (stock LinuxPPC R5) bug on ppc:
+
+	*dest++ = *src++;
+
+Bug report filed, fixed in egcs-1.1.2-12f.
+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/ 
+
+
+[LinuxPPC-R4, egcs-1.0.2]
+
+All compiling with -O2 is suspect, in particular guile-1.3, and
+Lily herself will break.
+
+
+[LinuxPPC, egcs-1.1b]
+
+Lilypond 1.1.35-1.1.51,...:  Wierd errors in guile scm_gc_mark ()
 
-[Linux Intel]
+
+[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
@@ -24,10 +65,22 @@ 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).  
+
+
+
+[Linux Intel]
 
-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.
+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.