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 segfault occurs as fast
as possible since "reverse execution" is actually tracing with full recording
in order to be able to "step backward". So even in the segfault case, an
example with minimal running time (rather than minimal source size though both
are usually correlated) is helpful.
---
** [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:16 PM UTC
**Owner:** Knut Petersen
**Attachments:**
-
[segfault.ly](https://sourceforge.net/p/testlilyissues/issues/5169/attachment/segfault.ly)
(14.5 kB; text/x-lilypond)
Current master segfaults on an openSuSE Tumbleweed system if a global staff
size equal or greater 14.5 is used. It also segfaulted with git master about
half a year ago, but I had/have no time to investigate the problem. Maybe
someone is interested.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
