Comment #8 on issue 2356 by [email protected]: Lilypond segfaults http://code.google.com/p/lilypond/issues/detail?id=2356
Well you do something like gdb out/bin/lilypond break some_subroutine_likely_called_not_all_too_much_before_the_segfault run foo.ly target record continue [wait for a long time] [segfault occurs] reverse-step [repeat until you get somewhere where the data and debugging makes sense again] _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
