-Document Really Ugly Bugs (coredumps, assert fails, etc)
+This documents serious bugs
-[Linux Intel]
+********
+
+[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]
+ }
+ }
+
+results in
+
+ lilypond: ../flower/include/varray.hh:141: struct Rhythmic_grouping *& Array<Rhythmic_grouping *>::elem(int) const: Assertion `i >=0&&i<size_' failed.
+
+And this
+
+ \score{
+ \melodic{
+ [c]
+ }
+ }
+
+in
+
+ 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
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]