On Sun, Feb 19, 2012 at 16:32, Phil Holmes <m...@philholmes.net> wrote: > ----- Original Message ----- From: "Przemysław Pawełczyk" > <prze...@gmail.com> > To: "Colin Hall" <colingh...@gmail.com> > Cc: "Phil Holmes" <m...@philholmes.net>; <bug-lilypond@gnu.org> > Sent: Sunday, February 19, 2012 2:51 PM > Subject: Re: Abrupt end of interpreting music (segmentation fault) > > > > Thank you, Colin, for CC-ing me. > > 2012/2/19 Colin Hall <colingh...@gmail.com>: >> >> On Sun, Feb 19, 2012 at 10:45:32AM -0000, Phil Holmes wrote: >>> >>> >Przemoc's example is not very long, but it involves lots of features. >>> >It would be good for anyone using a 64 bit system to try to reproduce >>> >the segfault (emergency early-stopping of LilyPond) and even better >>> >to start reducing the example to isolate the troublesome feature, >>> >if any. >>> >>> >>> I'm running 64 bit Vista and have no problem with the initial file. >>> I wonder if there's actually some faulty memory or something in his >>> machine? > > > The output of all 2.15.x version was verified by repeating the test > yesterday and running it today again. These are not some random > errors. > These tests were performed on my desktop computer > (http://wiki.przemoc.net/about/my_hardware) with Debian Wheezy 64-bit > using 64-bit version of LilyPond. > >> I can confirm that the initial file is fine on Windows 7 SP1 64-bit. > > > Today I tested: > - 64-bit LilyPond 2.15.30, work notebook (Dell Vostro 3750), Wheezy > x64 - segfault > - 32-bit LilyPond 2.15.30, desktop, Wheezy x64 - ok > - 32-bit LilyPond 2.15.27, desktop, Windows XP x64 - ok > > I'm sorry, because maybe I mixed things and possibly never run it on > Windows before. Damn. > Thus it looks like a 64-bit only problem. Not sure whether it's Linux > specific (Don't have FreeBSD). > > Regards. > > P.S. BTW Installation/extraction script could be improved (e.g. it > optimistically assumes that default shell is a full blown one, > supporting -s and -n in read invocations), so I could not extract it > in the first run. I'll hopefully send a fixed version next weekend. > > > Przemysław 'Przemoc' Pawełczyk > http://przemoc.net/ > > > ========================================== > > I don't normally install LilyPond on my Linux box - I simply run a > self-compiled version. It's 64-bit Ubuntu and on this, your file compiles > and runs fine. So I'm assuming (if you know better, please say) that this > is unlikely to be generic 64-bit, but Debian 64-bit specific. We'll > certainly pick it up as a bug, but it's likely to be hard to fix, bearing in > mind the fact that our standard development environment is Ubuntu.
If you run self-compiled version, and it's fine, then maybe just Linux x64 builds linked at lilypond.org are faulty? I've digged my VM image of Ubuntu 9.04 64-bit in VirtualBox, installed 64-bit LilyPond 2.15.30 and the segfault is there. So it's definitely not a Debian-specific issue. Regards. -- Przemysław 'Przemoc' Pawełczyk http://przemoc.net/ _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
