Re: Issue 1336 in lilypond: skipTypesetting segfaults when set during a skipBars-induced MultiMeasureRest spanner

[lilypond]

Comment #15 on issue 1336 by Carl.D.Sorensen: skipTypesetting segfaults  
when set during a skipBars-induced MultiMeasureRest spanner
http://code.google.com/p/lilypond/issues/detail?id=1336

Re Graham (comment 10):

No snarkiness taken.

Neil's earlier comment indicated this might not be the right way to solve  
things, so I was waiting for him.

After our recent discussion, I decided to play volleyball, instead of  
waiting.  So I put together a patch that used appropriate lilypond  
functions and would allow the layout to continue to completion, albeit with  
an error message.  It's probably not optimal, but it's the best I've been  
able to come up with so far.

In Neil's comment on the -devel thread,
<http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/32472>
he proposed another possible idea:

> See spanner.cc, lines 113-121.

> If this code doesn't exit the loop early, the crash goes away (since
> it allows the cloned spanner to exist outside its parent's bounds).

> Cheers,
> Neil

Perhaps we could bracket the continue statement in a test for  
Score.SkipBars, and only execute it if SkipBars were false.