Comment #7 on issue 1336 by percival.music.ca: skipTypesetting segfaults
when set during a skipBars-induced MultiMeasureRest spanner
http://code.google.com/p/lilypond/issues/detail?id=1336
Depends what you mean by "root cause". :)
There's two ways of debugging this kind of thing: the intelligent way, and
the stupid way.
Intelligent: think about the lilypond internals, the data structures, the
architecture, etc. Figure out which object/engraver/translator is
misbehaving.
Stupid: this segfault comes from trying to use a NULL pointer. So figure
out where that NULL pointer is coming from, by tracing back through the
backtrace, ading printf() statements where appropriate, and comparing the
text output from a successful program run (with a slightly modified input
file), and the segfault program run.
You're thinking about it in the intelligent way. I've been working through
it in the stupid way. Partly because I have relatively little knowledge of
our internals, but partly because I've been working on this when my brain
is fried from other stuff.
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
