release: 0.1.21

[lilypond.git] / BUGS

diff --git a/BUGS b/BUGS
index c5f7e685f6bf20307828f7b2887d27f2ac5b053d..40be3fcf2895f97369cf4522f400cb4e46261e4f 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1,47 +1,33 @@
-Document reintroduced deficiencies.
-
-* placement of bar-numbers
-
-**************** 
-vi1=\melodic{
-  \meter 4/4;
-  \octave c'';
-
-  B8 G G G16 A B8 G G G16 A | 
-       
-}
-
-vi2=\melodic{
-  \meter 4/4;
-  \octave c'';
-
- r16
-}
-
-%{
-bc=\melodic{
-  \clef "bass";
-  \meter 4/4;
-  \octave c;
-
-  G1 |
-}
-%}
-
-\score{
-  < \multi 3;
-    \vi1
-    \vi2
-
-  >
-
-  \paper{
-    geometric=1.2;
-    unitspace=8.\mm;
-    linewidth=18.\cm;
-    gourlay_maxmeasures=4.;
-    gourlay_energybound = 70000.;
-       basicspace = 2.8\pt;
-  }
-}
-***************************
+Document Really Ugly Bugs (coredumps, assert fails, etc)
+
+
+[Linux Intel]
+
+LilyPond occasionally crashes while parsing the initialisation files.
+This is a very obscure bug, and usually entering the commandline
+differently "fixes" it.
+
+       lilypond input.ly 
+
+and
+
+       lilypond -I. ./input.ly 
+
+makes a difference
+
+Typical stacktrace:
+
+       SIGSEGV
+       __libc_malloc (bytes=16384)
+       ?? ()
+       yyFlexLexer::yy_create_buffer ()
+       Includable_lexer::new_input (this=0x8209a00, s={strh_ = {
+               :
+
+
+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.
+
+