anders.vin...@bek.no writes: > a> a4cc910a Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert > > With the change from -NDEBUG to -DEBUG in commit <a4cc910a>, quite a few > scores makes lilypond crash. The same happens with releases since then > (19.21++). The behavior is the same whether DEBUG is on or off when > compiling. > > The crashes i've seen are located to some 'assert's not passing, > suggesting bugs or faulty execution in other places in lilypond. These > asserts are not inside "#ifdef DEBUG" (or "#ifndef NDEBUG" previously). > Unfortunately i'm totally helpless about anything gcc/g++, thus no idea > why this change of flags makes the asserts kick in.
assertions are globally disabled by -DNDEBUG which makes NDEBUG a bad idea since assertions are supposed for cases where the program has no suitable recourse. The triggering assertions should likely as a first measure be replaced by programming errors and fixed at some point of time. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
