Re: segfault in grob.cc

[John Galbraith]

   ok. So we should get rid of system, and call lilypond using exec()
   directly. FWIW, I usually run LilyPond with 1 meg of stack space.

The ulimit hack also works - I'm all for whatever you think is cleanest.

   > What is a broken smob, anyway?  Is it possible that my score has some
   > diabolical feature that makes a bunch of those?

   Lily constructs  the score as one very long line (or system). After
   line breaking, this long line is broken into the lines which are
   printed, and spanners (slurs, ties, etc.) are broken along. This
   linebreaking requires that lots of pointers have to be remapped, which
   is what handle_broken_smobs () does.

A really high estimate for me would be 800 measures with a linebreak
every five, and 12 staves.  If I had a meter change at every
linebreak, that would still only be 1920 (x2 for each part?) broken "smobs".
In reality, a lot of those staves are blown away by the HaraKiri mechanism.
Would it help you guys if I hacked in some kind of counter?

John