Am 09.09.2016 um 09:24 schrieb Mark Knoop:
> At 01:57 on 09 Sep 2016, Thomas Morley wrote:
>> 2016-09-09 0:13 GMT+02:00 Simon Albrecht <simon.albre...@mail.de>:
>> _Cannot_ confirm crash with a build from most recent master, i.e from:
>> commit 5944d20489bb5b8e4c4907fa3b3bcae9ec275ccb
>>
>> with:
>> gcc --version
>> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.2) 5.4.0 20160609
> I reduced Urs' example to this:
>
> { fis'1 ~ -> }
>
> which does result in a Segmentation fault (core dumped) on 2.19.47 but
> compiles fine on current git. I presume David's commit 93f3d6 is what
> fixed this.
>
> {
> % 2.19.47
> fis'1 ~ -> % seg fault
> %fis'1 ~ % compiles
> %fis'1 ~ -> fis'1 ~ % compiles
> %fis'1 ~ -> fis'1 ~ g' % compiles
> %fis'1 -> % compiles
>
> % 2.19.48 current git
> %fis'1 ~ -> % compiles
> %fis'1 ~ % compiles
> %fis'1 -> % compiles
> %fis'1 ~ -> fis'1 ~ % compiles
> %fis'1 ~ -> fis'1 ~ g' % compiles
> }
>
Indeed, I can verify this. Thanks for trying.
I didn't think about recompiling LilyPond because the file I derived
this MWE from had actually crashed for a long time ago, so I wouldn't
have thought that the issue had *just* been fixed in between the latest
release and current master ...
So obviously this isn't a bug anymore.
Urs
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
