[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Segfault from unusual time signatures
From: |
Keith OHara |
Subject: |
Re: Segfault from unusual time signatures |
Date: |
Sat, 27 Dec 2014 22:56:55 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Dan Eble <nine.fierce.ballads <at> gmail.com> writes:
> > >>> % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15.
> > >>> \version "2.19.0"
> > >>> \new Staff {
> > >>> \relative d' {
> > >>> \time 8/1024 d128 |
> > >>> \time 99999/1 d1
> > >>> }
> > >>> }
David Kastrup writes:
> > > You are both omitting the most relevant detail: 32bit or 64bit system?
>
> The crash log has a line with the message
> "Thread 0 crashed with X86 Thread State (32-bit):"
> but I don't know if that means the application is 32-bit
> or just that the register table it was about to dump was 32 bit (which it
was).
>
This looks distinct the other reported shortcomings, and shows up
with less than one million (short-scale) beats in the measure.
Added at <https://code.google.com/p/lilypond/issues/detail?id=4231>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Segfault from unusual time signatures,
Keith OHara <=