>>>>> On Tue, 27 Oct 2015 12:18:27 +1100, Andrew Bernard
>>>>> <[email protected]> said:
A> Using 2.19.30, hoping to avoid the core dumps from 2.19.29, I get
A> the following error on my moderately large score: Preprocessing
A> graphical objects...lilypond:
A>
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227:
A> T Interval_t<T>::center() const [with T = double]: Assertion
A> `!is_empty ()' failed. Exited with exit status 1.
I'm hitting the same break here (also in a complex score). The commit
which makes it break is from May:
a4cc910a Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert
The commit is empty, but message indicates some flags vs. debugging or
optimisation related to asserting things were being changed, which fits
well with the break message. What was changed which might be looked
into?
I tried tuning some flags with current sources, without getting
anywhere. Is there something to pass to ../configure to get rid of
(this) asserts?
Thanks,
-anders
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
