[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failed assertion in 2.3.18
From: |
Russ Ross |
Subject: |
Re: failed assertion in 2.3.18 |
Date: |
Sun, 3 Oct 2004 18:03:55 +0100 |
I tested 2.3.20 and it still crashes on a bunch of scores.
- Russ
On Wed, 29 Sep 2004 21:06:39 +0100, Russ Ross <address@hidden> wrote:
> I'm getting segmentation faults now, with those two scores and with
> several other smaller ones. Not sure if its related to the fix or
> something different.
>
> I can successfully compile several others, so it is probably something
> more than a completely broken installation on my machine.
>
> One of the scores that causes it to crash is here:
>
> http://www.russross.com/music/lilypond-crash.tar.gz
>
> It contains two files and can be compiled using:
>
> lilypondfullscore.ly
>
> This is the full version of the score I used to generate the original
> test case. It had the failed assert before and has the segfault now.
>
> - Russ
>
>
>
>
> On Wed, 29 Sep 2004 01:37:22 +0200, Erik Sandberg
> <address@hidden> wrote:
> > On Thursday 23 September 2004 18.33, Russ Ross wrote:
> > > I just compiled 2.3.18 on a Debian system and got this error:
> > >
> > > lilypond: ../flower/include/array.hh:149: T& Array<T>::elem_ref(int)
> > > const [with T = void*]: Assertion `i >=0&&i<size_' failed.
> >
> > Seems to be fixed in 2.3.19. Can you verify with your big scores?
> >
> > Erik
> >
>
- Re: failed assertion in 2.3.18,
Russ Ross <=