Well, in this particular case I have to say that the situation at a segfault
makes a minimal example often less necessary for analysis than in other cases
since the debugger will provide a lot of information. However, once one needs
to work with reverse execution, it's important that the segfau
Maybe something like that should be added to the documentation:
"If you do not see how to transform a correct but segfaulting lilypond source
file into a tiny still segfaulting example use a monte carlo search until you
succeed or don't report the problem."
---
** [issues:#5169] Segfault afte
If you'd spent about 2 minutes at least making an effort to simplify this file
you'd have noticed that as soon as you remove all the '\break' statements - or
rather I removed the 'obreak' command you created and the corresponding strings
in your huge file, then it compiles fine. But with the 'br
---
** [issues:#5169] Segfault after "cannot find line breaking that satisfies
constraints"**
**Status:** New
**Created:** Sat Jul 29, 2017 07:40 AM UTC by Knut Petersen
**Last Updated:** Sat Jul 29, 2017 07:40 AM UTC
**Owner:** Knut Petersen
**Attachments:**
-
[segfault.ly](https://sourcef
