Re: Strange LilyPond crash

> Here's the file... Edski-2015-11-16_v4_test.ly > st.ly> No problem compiling this file and creating a PDF using the current LilyPond 2.19.32 running from inside Frescobaldi 2.18.1 on an ArchLinux x86_64 running a Kernel

Re: Strange LilyPond crash

2015-11-25 20:30 GMT+01:00 Edward Ardzinski : > Here's the file... Edski-2015-11-16_v4_test.ly > lilypond Edski-2015-11-16_v4_test.ly GNU LilyPond 2.18.2 Processing `Edski-2015-11-16_v4_test.ly' Parsing... Interpret

Re: Strange LilyPond crash

Here's the file... Edski-2015-11-16_v4_test.ly <http://lilypond.1069038.n5.nabble.com/file/n184124/Edski-2015-11-16_v4_test.ly> -- View this message in context: http://lilypond.1069038.n5.nabble.com/Strange-LilyPond-crash-tp183610p184124.html Sent from the User mailing list

Re: Strange LilyPond crash

Edward Ardzinski writes: > I don't know if I'm stumbling on something similar, but I can't believe that > it's a large file issue - the piece is about 50 bars of mostly slow 7 with a > repeat unfolded, two voices and a 2 part drum staff, no lyrics, and done > entirely with 2.18.2 Not the same bu

Re: Strange LilyPond crash

Am 24.11.2015 um 17:11 schrieb David Kastrup: Marc Hohl writes: Am 24.11.2015 um 00:12 schrieb Thomas Morley: [...] So, commit b416f10429d8d3881445d9000ff422dc67176df1 Author: David Kastrup Date: Wed Jul 15 23:30:30 2015 +0200 Issue 3693: Let Percent_repeat_iterator be unfazed by T

Re: Strange LilyPond crash

015-11-16 v4 test.ly' Parsing... Interpreting music...[8][16][24][32] Exited with return code -1073741819. Eventually I added the drums, the pdf works fine. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Strange-LilyPond-crash-tp183610p184079.html Sent from the Use

Re: Strange LilyPond crash

2015-11-24 17:11 GMT+01:00 David Kastrup : [...] > > Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4670/ > > -- > David Kastrup You already pushed it, so I tested Marc's files with a build including your patch. As far as I can tell, all works fine now. Many thanks, Har

Re: Strange LilyPond crash

Marc Hohl writes: > Am 24.11.2015 um 00:12 schrieb Thomas Morley: > [...] >> >> So, >> commit b416f10429d8d3881445d9000ff422dc67176df1 >> Author: David Kastrup >> Date: Wed Jul 15 23:30:30 2015 +0200 >> >> Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes >> >> The

Re: Strange LilyPond crash

Am 24.11.2015 um 00:12 schrieb Thomas Morley: [...] So, commit b416f10429d8d3881445d9000ff422dc67176df1 Author: David Kastrup Date: Wed Jul 15 23:30:30 2015 +0200 Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes There is still one shortcoming: the percent repea

Re: Strange LilyPond crash

2015-11-22 1:59 GMT+01:00 Thomas Morley : > 2015-11-21 17:31 GMT+01:00 Thomas Morley : >> 2015-11-21 16:42 GMT+01:00 David Kastrup : >>> Marc Hohl writes: >>> As soon as I remove an instrumental part at random (or even some notes), the crash may or may not disappear. I am not sure but II

Re: Strange LilyPond crash

Marc Hohl writes: > Am 21.11.2015 um 16:54 schrieb David Kastrup: >> Marc Hohl writes: >> >>> Am 21.11.2015 um 10:53 schrieb David Kastrup: Marc Hohl writes: >>> [...] Looks like there is some sequential iterator consulted for pending_moment that no longer has an iter_ to refer t

Re: Strange LilyPond crash

Am 21.11.2015 um 16:54 schrieb David Kastrup: Marc Hohl writes: Am 21.11.2015 um 10:53 schrieb David Kastrup: Marc Hohl writes: [...] Looks like there is some sequential iterator consulted for pending_moment that no longer has an iter_ to refer to. More likely than not, one of the fixes f

Re: Strange LilyPond crash

Marc Hohl writes: > Am 21.11.2015 um 10:53 schrieb David Kastrup: >> Marc Hohl writes: > [...] >> Looks like there is some sequential iterator consulted for >> pending_moment that no longer has an iter_ to refer to. >> >> More likely than not, one of the fixes for addlyrics going off the deep >>

Re: Strange LilyPond crash

2015-11-21 17:31 GMT+01:00 Thomas Morley : > 2015-11-21 16:42 GMT+01:00 David Kastrup : >> Marc Hohl writes: >> >>> As soon as I remove an instrumental part at random (or even some >>> notes), the crash may or may not disappear. I am not sure but IIRC a >>> file that compiled fine during one run c

Re: Strange LilyPond crash

2015-11-21 16:42 GMT+01:00 David Kastrup : > Marc Hohl writes: > >> As soon as I remove an instrumental part at random (or even some >> notes), the crash may or may not disappear. I am not sure but IIRC a >> file that compiled fine during one run crashed without having done any >> changes to that

Re: Strange LilyPond crash

Marc Hohl writes: > As soon as I remove an instrumental part at random (or even some > notes), the crash may or may not disappear. I am not sure but IIRC a > file that compiled fine during one run crashed without having done any > changes to that specific file (nor its includes). Is it possible

Re: Strange LilyPond crash

Am 21.11.2015 um 10:53 schrieb David Kastrup: Marc Hohl writes: [...] Looks like there is some sequential iterator consulted for pending_moment that no longer has an iter_ to refer to. More likely than not, one of the fixes for addlyrics going off the deep end when its associated context dies

Re: Strange LilyPond crash

Marc Hohl writes: > Am 17.11.2015 um 00:24 schrieb David Kastrup: >> Marc Hohl writes: >> >>> Hi list, >>> >>> I am currently reworking some older stuff that compiled perfectly >>> under 2.13.x >>> >>> Yes, I used convert-ly on all files, but nevertheless, I encountered a >>> strange problem: >>

Re: Strange LilyPond crash

Am 17.11.2015 um 00:24 schrieb David Kastrup: Marc Hohl writes: Hi list, I am currently reworking some older stuff that compiled perfectly under 2.13.x Yes, I used convert-ly on all files, but nevertheless, I encountered a strange problem: I have a drum part, consisting of an upper and a lo

Re: Strange LilyPond crash

Marc Hohl writes: > Hi list, > > I am currently reworking some older stuff that compiled perfectly > under 2.13.x > > Yes, I used convert-ly on all files, but nevertheless, I encountered a > strange problem: > > I have a drum part, consisting of an upper and a lower DrumVoice, and > if I try to c

Re: Strange LilyPond crash

On 16.11.2015 11:27, Marc Hohl wrote: Hi list, I am currently reworking some older stuff that compiled perfectly under 2.13.x Yes, I used convert-ly on all files, but nevertheless, I encountered a strange problem: I have a drum part, consisting of an upper and a lower DrumVoice, and if I

Strange LilyPond crash

Hi list, I am currently reworking some older stuff that compiled perfectly under 2.13.x Yes, I used convert-ly on all files, but nevertheless, I encountered a strange problem: I have a drum part, consisting of an upper and a lower DrumVoice, and if I try to compile the full Drum score, I g

Re: LilyPond crash (was: font size for numbers on easyHeadOn with number)

On 10/8/10 6:46 AM, "MING TSANG" wrote: > I further do some testing and discover that the culprit that give me the item > #1 problem on the below email is: > > R1^\markup{Andante Graccoso} | R1 | R1 | a'1\rest \fermata | > %bar 01-04 > > I change the previous line as: > > r1^\marku

RE: Lilypond crash

d-user-bounces+nick.payne=internode.on@gnu.org] On > Behalf Of Michael Käppler > Sent: Saturday, 11 April 2009 17:25 > To: M Watts > Cc: lilypond-user@gnu.org; Nick Payne > Subject: Re: Lilypond crash > > Hi Nick, > I'm able to reproduce this on OpenSuse 11.0 with LilyP

Re: Lilypond crash

Hi Nick, I'm able to reproduce this on OpenSuse 11.0 with LilyPond 2.13, too. I don't know if there's a more simple way, but try this instead: i = #(define-music-function (parser location) () (apply make-music (append (list 'StrokeFingerEvent 'ori

Re: Lilypond crash

Nick Payne wrote: I was attempting to shorten the entry required for indicating strokefingering: \version "2.12.2" i = #(define-music-function (parser location) () #{ \rightHandFinger #2 #}) \relative c' { } This causes Lilypond to crash (2.12.2, Windows). The entry in the applicatio

Lilypond crash

I was attempting to shorten the entry required for indicating strokefingering: \version "2.12.2" i = #(define-music-function (parser location) () #{ \rightHandFinger #2 #}) \relative c' { } This causes Lilypond to crash (2.12.2, Windows). The entry in the application event log shows:

Re: lilypond crash

gt; problem on my system (Vista), and which became available today. > > Trevor D > > - Original Message - > From: "Stefan Thomas" <[EMAIL PROTECTED]> > To: "lilypond-user" > Sent: Friday, March 28, 2008 9:31 PM > Subject: lilypond crash &g

Re: lilypond crash

t; <[EMAIL PROTECTED]> To: "lilypond-user" Sent: Friday, March 28, 2008 9:31 PM Subject: lilypond crash Dear Lilypond-users, I have a problem with my Laptop, on which I use Windows XP. When I run the test.ly I get the following message: %lilypond %args "C:\Dokumente und Einstellun

lilypond crash

Dear Lilypond-users, I have a problem with my Laptop, on which I use Windows XP. When I run the test.ly I get the following message: %lilypond %args "C:\Dokumente und Einstellungen\Stefan\Desktop\test.ly" »C:/Dokumente und Einstellungen/Stefan/Desktop/test.ly« wird verarbeitet Analysieren... Int

LilyPond crash on FC3

Op do, 28-04-2005 te 12:51 -0400, schreef Stan Mulder: > [stan~]$ lilypond > GNU LilyPond 2.5.21 > Segmentation fault > > [stan~]$ gdb /usr/bin/lilypond > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1208071456 (LWP 6201)] > 0x00afa21e in scm_mark_subr_table () fro

Lilypond crash

I just upgraded to SuSE 9.2 and installed the lilypond 2.2.6 package, This is on an Athlon-64 based system, and is installed from the X64 RPM builds. I got the following message when I attempted to run a sample program that came in the RPM: $ lilypond /usr/share/doc/packages/lilypond/input/tw

Re: Lilypond crash on Windows 98 SE.

Jonathan Scott writes: > I just installed Lilypond 2.0.1 on Windows 98 SE. The cygwin install > process downloaded about 52MB and installed OK and I didn't see > anything wrong. However, when I try to run the sample, it crashes. > I guess this could be a cygwin problem rather than LilyPond its

Lilypond crash on Windows 98 SE.

I just installed Lilypond 2.0.1 on Windows 98 SE. The cygwin install process downloaded about 52MB and installed OK and I didn't see anything wrong. However, when I try to run the sample, it crashes. I guess this could be a cygwin problem rather than LilyPond itself but as I know nothing about