Re: Segfault with slur over tie 2.18.2

2019-09-05 Thread Jason Miller
I was unable to get it to reproduce again on ubuntu, I suspect I was just SSH'd into the wrong machine or something. Sorry for wasting your time on that. After debugging the issue, it appears to be the same as https://sourceforge.net/p/testlilyissues/issues/4814/ I've submitted a patch to NixOS

Re: Segfault with slur over tie 2.18.2

2019-09-01 Thread Aaron Hill
On 2019-09-01 7:50 pm, Jason Miller wrote: On Sun, 01 Sep 2019 16:45:16 -0700, Aaron Hill wrote: On 2019-09-01 3:44 pm, Jason Miller wrote: > See attached example. This was originally encountered on nixos, but I > confirmed it also happens on Ubuntu. Is this a valid case? The code as attache

Re: Segfault with slur over tie 2.18.2

2019-09-01 Thread Jason Miller
On Sun, 01 Sep 2019 16:45:16 -0700, Aaron Hill wrote: > On 2019-09-01 3:44 pm, Jason Miller wrote: > > See attached example. This was originally encountered on nixos, but I > > confirmed it also happens on Ubuntu. > > Is this a valid case? The code as attached appears to be malformed: Sorry, I

Re: Segfault with slur over tie 2.18.2

2019-09-01 Thread Aaron Hill
On 2019-09-01 3:44 pm, Jason Miller wrote: See attached example. This was originally encountered on nixos, but I confirmed it also happens on Ubuntu. Is this a valid case? The code as attached appears to be malformed: GNU LilyPond 2.19.83 Processing `foo.ly' Parsing... foo.ly:6:3: error

Segfault with slur over tie 2.18.2

2019-09-01 Thread Jason Miller
See attached example. This was originally encountered on nixos, but I confirmed it also happens on Ubuntu. \version "2.18.2" \new Staff { f8( e~ e2.) | } >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/