[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: Segfault from unusual time signatures
From:       Keith OHara <k-ohara5a5a () oco ! net>
Date:       2014-12-27 22:56:55
Message-ID: loom.20141227T235255-430 () post ! gmane ! org
[Download RAW message or body]

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>



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
[prev in list] [next in list] [prev in thread] [next in thread]