Re: .ly file partially compiles, then LP crashes

2017-07-29 9:53 GMT+02:00 Knut Petersen : > Am 29.07.2017 um 09:01 schrieb David Kastrup: >> >> >> Uh, the proper way to throw in the towel is not a segfault. If you can >> find a reproducible manner of segfaulting on a hard page break problem, >> that warrants fixing.

Re: .ly file partially compiles, then LP crashes

Knut Petersen writes: > Am 29.07.2017 um 09:01 schrieb David Kastrup: >> >> Uh, the proper way to throw in the towel is not a segfault. If you can >> find a reproducible manner of segfaulting on a hard page break problem, >> that warrants fixing. > > I remember

Re: .ly file partially compiles, then LP crashes

Am 29.07.2017 um 09:01 schrieb David Kastrup: Uh, the proper way to throw in the towel is not a segfault. If you can find a reproducible manner of segfaulting on a hard page break problem, that warrants fixing. I remember segfaults that looked exactly like Guys, but those scores have

Re: .ly file partially compiles, then LP crashes

Knut Petersen writes: > Hi Guy! > >> Starting lilypond-windows.exe 2.19.56 >> [Leloupgarou_transformationscene-pianoReduction.ly]... >> >> Processing `[filename].ly' >> >> Parsing... >> >> Interpreting >>

Re: .ly file partially compiles, then LP crashes

Hi Guy! Starting lilypond-windows.exe 2.19.56 [Leloupgarou_transformationscene-pianoReduction.ly]... Processing `[filename].ly' Parsing... Interpreting

Re: .ly file partially compiles, then LP crashes

Guy Stalnaker writes: > And it happened twice more, too. Any reason you are using an old development version? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org

Re: .ly file partially compiles, then LP crashes

And it happened twice more, too. Last time I tried to add \clef "treble" and then \clef bass to the score and the same seg-fault/error recurred. A quick test showed that just adding \clef "treble" was enough to cause the seg-fault (if that's what is happening). Nothing I can do to make that

Re: .ly file partially compiles, then LP crashes

Am 28.07.2017 um 18:56 schrieb David Kastrup: > David Wright writes: > >> On Fri 28 Jul 2017 at 15:16:03 (+0200), David Kastrup wrote: >>> Bernhard Kleine writes: >>> Am 28.07.2017 um 00:55 schrieb Guy Stalnaker: > Exited with return

Re: .ly file partially compiles, then LP crashes

David Wright writes: > On Fri 28 Jul 2017 at 15:16:03 (+0200), David Kastrup wrote: >> Bernhard Kleine writes: >> >> > Am 28.07.2017 um 00:55 schrieb Guy Stalnaker: >> >> Exited with return code -1073741819 >> > This has come up with the same

Re: .ly file partially compiles, then LP crashes

On Fri 28 Jul 2017 at 15:16:03 (+0200), David Kastrup wrote: > Bernhard Kleine writes: > > > Am 28.07.2017 um 00:55 schrieb Guy Stalnaker: > >> Exited with return code -1073741819 > > This has come up with the same number IIRC repeatedly. > > It's Windows' helpful way

Re: .ly file partially compiles, then LP crashes

Bernhard Kleine writes: > Am 28.07.2017 um 00:55 schrieb Guy Stalnaker: >> Exited with return code -1073741819 > This has come up with the same number IIRC repeatedly. It's Windows' helpful way to refer to a segfault. Storing something more descriptive like

Re: .ly file partially compiles, then LP crashes

It's Hex C005. Probably an access violation. -- Phil Holmes - Original Message - From: Bernhard Kleine To: lilypond-user@gnu.org Sent: Friday, July 28, 2017 1:36 PM Subject: Re: .ly file partially compiles, then LP crashes Am 28.07.2017 um 00:55 schrieb Guy

Re: .ly file partially compiles, then LP crashes

Am 28.07.2017 um 00:55 schrieb Guy Stalnaker: > Exited with return code -1073741819 This has come up with the same number IIRC repeatedly. I wonder where the return code comes from. If there is such a message there is a reason for it that someone programmed. (given that such a message is totally

Re: .ly file partially compiles, then LP crashes

Thomas Morley writes: > Occasionally I had smiliar problems, with files I was working on. > Eventually I must have added some whitespace-characters at unfortunate > place without noticing. > Because it worked again after doing "Remove Trailing Whitespace" > (provided by

Re: .ly file partially compiles, then LP crashes

2017-07-28 1:16 GMT+02:00 Guy Stalnaker : > Simon, > > That was my tack -- the dirty way was to slowly comment out sections and see > what happened. It's the oddest thing. I'm writing a piano reduction mostly > from string parts, so I'm doing this: > > > pianoRH = { > << {

Re: .ly file partially compiles, then LP crashes

Hi Guy, > I'm writing a piano reduction mostly from string parts, so I'm doing this: > > > pianoRH = { > << { ViolinI } \\ { ViolinII } >> > } > pianoLH = { > << { Violo } \\ { Cello } >> > } > > > As shown, did not compile. Have you thought about trying the partcombiner? Or at least

Re: .ly file partially compiles, then LP crashes

Simon, That was my tack -- the dirty way was to slowly comment out sections and see what happened. It's the oddest thing. I'm writing a piano reduction mostly from string parts, so I'm doing this: pianoRH = { << { ViolinI } \\ { ViolinII } >> } pianoLH = { << { Violo } \\ { Cello } >> }

Re: .ly file partially compiles, then LP crashes

On 28.07.2017 00:55, Guy Stalnaker wrote: I'm not trying to figure out how to do something here. This is a code file that compiled to midi/pdf output a few hours ago (last successful pdf output at 4:31p CDT). Can you restore the file version that compiled successfully? Or is there any other