"Thomas Morley" <[email protected]> writes:

> Occurs between 2.19.20 and 2.19.21.

Red herring.

commit a4cc910a3401d25bb94ff0ecb4dc18f681c71004
Author: David Kastrup <[email protected]>
Date:   Tue May 12 19:01:57 2015 +0200

    Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert
    
    The compiler option -DNDEBUG is no longer being used: -DNDEBUG disables
    the assert function, and assert is essentially stating that the program
    cannot useful continue if the assertion is not met.  -DNDEBUG is
    basically an option for compiling an application to a limited amount of
    ROM when aborting with a diagnostic is not preferable to crashing.
    
    This is not the case for LilyPond.  So expensive debugging options now
    are enabled with -DDEBUG instead.  There is a new configure option
    --enable-checking defaulting to "off" for this now.
    
    At the current point of time, setting --disable-optimising also has the
    effect of enabling the checks: this will be retained until Patchy has
    been adapted to using --enable-checking.

is 2.19.21 so if you actually want to find out what problem might be
there, you need to configure using --disable-optimising (for example)
for versions older than that.

-- 
David Kastrup


---

** [issues:#5651] Core dump: /lily/page-breaking.cc, Line 1052**

**Status:** New
**Labels:** Regression 
**Created:** Sat Jan 04, 2020 01:39 PM UTC by pkx166h
**Last Updated:** Sat Jan 04, 2020 02:25 PM UTC
**Owner:** nobody


On 27/12/2019 19:19, [email protected] wrote:
> Code below works fine when run under windows in lilypond 2.18.2
> However when running in 2.19.83, or in 2.21.0 (version end November) an
> assertion is thrown:
>
> File:
> /home/jaap/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-master
> /lily/page-breaking.cc, Line 1052
> Expression: my_index == 0
>

~~~
 \version "2.18.2"
 
\header {
title = "Title"
}

\relative fis' { 
\pageBreak
r1 \break
r4 r4 r2
r2 r4 c4 \break
r1 \pageBreak
r1 
}
~~~


---

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.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to