Hello, On Sat, Oct 1, 2011 at 6:01 PM, m...@apollinemike.com <m...@apollinemike.com> wrote: > On Oct 1, 2011, at 6:53 PM, Neil Puttock wrote: > >> Hey guys, >> >> I can't complete test-baseline due to an assertion error running >> mozart-hrn-3.ly. Here's the backtrace: >> >> Drawing systems...lilypond: ../flower/include/interval.hh:226: T >> Interval_t<T>::center() const [with T = double]: Assertion `!is_empty >> ()' failed. >> >> Program received signal SIGABRT, Aborted. >> >> (gdb) bt >> #0 0x00007ffff508fd05 in raise (sig=6) >> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 >> #1 0x00007ffff5093ab6 in abort () at abort.c:92 >> #2 0x00007ffff50887c5 in __assert_fail (assertion=0x70bd60 "!is_empty ()", >> file=<value optimised out>, line=226, function=<value optimised out>) >> at assert.c:81 >> #3 0x000000000041bf01 in Interval_t<double>::center (this=0x7fffffff7310) >> at ../flower/include/interval.hh:226 >> #4 0x00000000006d8b2c in Tuplet_number::calc_y_offset (smob=0x7ffff22bebe0) >> at tuplet-number.cc:83 >> #5 0x00007ffff7926ae4 in scm_dapply () from /usr/lib/libguile.so.17 >> #6 0x00000000004fc65f in Grob::try_callback_on_alist (this=0x108d150, >> alist=0x108d1b0, sym=0x7ffff2a6c080, proc=0x7ffff45ac530) >> at grob-property.cc:231 >> #7 0x00000000004fc398 in Grob::internal_get_property (this=0x108d150, >> sym=0x7ffff2a6c080) at grob-property.cc:188 >> #8 0x0000000000505efd in Grob::get_offset (this=0x108d150, a=Y_AXIS) >> at grob.cc:383 >> #9 0x0000000000505a67 in Grob::relative_coordinate (this=0x108d150, >> refp=0x184dc00, a=Y_AXIS) at grob.cc:312 >> #10 0x00000000005062a4 in Grob::extent (this=0x108d150, refp=0x184dc00, >> a=Y_AXIS) at grob.cc:427 >> #11 0x000000000043a1ad in add_boxes (me=0x108d150, x_common=0x18950a0, >> >> Looks like the new tuplet collision avoidance code. >> >> Cheers, >> Neil > > Hey Neil, > > I just ran mozart-hrn-3.ly on an unoptimized binary and could not reproduce > the problem. Could someone else please verify? > > Cheers, > MS > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel >
I don't get what Neil gets but when I run make -j7 CPU_COUNT=7 test-baseline on a '--disable-optimsed' out of tree build for the latest commit 4f49b000d6e257724e311b406e2346b8388c1f0e I get --snip-- possibilities for bes: (bes besT) possibilities for f: (f fT) possibilities for fis: (fis fisT) possibilities for gis: (gis gisT) possibilities for thumb-bes: (thumb-bes thumb-besT) possibilities for thumb-e: (thumb-e thumb-eT) possibilities for thumb-fis: (thumb-fis thumb-fisT) job 4 terminated with signal: 6 job 3 terminated with signal: 6 etc. --snip-- I can't see where it is failing. The possibilities for bes: (bes besT) possibilities for f: ... I always get when making a test-baseline or check so I know they are nothing to do with this... but it just borks at this point along the make process. Neil what command do you run when you do a test-baseline so that I might get something like you do? -- -- James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel