Re: Abrupt end of interpreting music (segmentation fault)

[Przemysław Pawełczyk]

Hi Eluze and Phil,

I did not get your responses. maybe you forgot that
> P.S. Please add me to CC as I'm not on the list.

>> If I run this from the Windows command line, it compiles without problem.
>> Do you think it might have anything to do with articulate?  The other
>> strange thing is the bar-check fails in your output - I don't see those,
>> either.

Removing articulate is just another way to get rid of segfault.

> these bar-check errors vanish between 2.15.11 and 2.15.19 ( I haven't loaded
> all the versions between).
>
> removing \resetRelativeOctave makes 2.15.10 compile without complaining.
>
> (this under windows 7)

In my case removing all \resetRelativeOctave instances does not help at all.

I've provided some more information at:
http://paste.przemoc.net/lilypond/abrupt-end-of-interpreting-music/

- lilypond-2.15.30.ltrace-last-10334-lines.bz2
- lilypond-2.14.2+2.15.x.out-not-redirected
- lilypond-2.14.2+2.15.x.summary

Below you can find the same summary:
GNU LilyPond 2.14.2  - warnings
GNU LilyPond 2.15.0  - warnings
GNU LilyPond 2.15.1  - warnings
GNU LilyPond 2.15.2  - warnings
GNU LilyPond 2.15.3  - warnings
GNU LilyPond 2.15.4  - warnings
GNU LilyPond 2.15.5  - warnings
GNU LilyPond 2.15.6  - warnings
GNU LilyPond 2.15.7  - warnings
GNU LilyPond 2.15.8  - warnings
GNU LilyPond 2.15.9  - warnings
GNU LilyPond 2.15.10 - warnings
GNU LilyPond 2.15.11 - ok
GNU LilyPond 2.15.12 - ok
GNU LilyPond 2.15.13 - ok
GNU LilyPond 2.15.14 - ok
GNU LilyPond 2.15.15 - ok
GNU LilyPond 2.15.16 - ok
GNU LilyPond 2.15.17 - ok
GNU LilyPond 2.15.18 - ok
GNU LilyPond 2.15.19 - ok
GNU LilyPond 2.15.20 - ok
GNU LilyPond 2.15.21 - ok
GNU LilyPond 2.15.22 - ok
GNU LilyPond 2.15.23 - segfault
GNU LilyPond 2.15.24 - segfault
GNU LilyPond 2.15.25 - segfault
GNU LilyPond 2.15.26 - segfault
GNU LilyPond 2.15.27 - segfault
GNU LilyPond 2.15.28 - ok
GNU LilyPond 2.15.29 - ok
GNU LilyPond 2.15.30 - segfault

I included warnings only for completeness, but they aren't important
in this issue (errors in articulate script are responsible for them).

BTW I'm using 64-bit releases, forgot to mention it before.

Regards.

-- 
Przemysław 'Przemoc' Pawełczyk
http://przemoc.net/