lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Manual page breaking causing assertion failure


From: Chris Yate
Subject: Fwd: Manual page breaking causing assertion failure
Date: Sat, 9 Jan 2016 13:18:12 +0000

In case anyone here is interested (perhaps Ralph), a Minimal not-Working Example I've sent to the bugs list.

---------- Forwarded message ----------
From: Chris Yate <address@hidden>
Date: 9 January 2016 at 09:55
Subject: Re: Manual page breaking causing assertion failure
To: tisimst <address@hidden>
Cc: address@hidden


So, it turns out this was easy to minimise the code. File is attached. It's still ~70 bars but only one voice, which is the dynamics staff of a piano score (without anything else), so it's only silent music.

"AutoPageBreaksOff" in the score block causes the exception failure. 

I note some "insane spring distance" warnings.These don't happen in the real thing.

Chris


On 9 January 2016 at 09:05, Chris Yate <address@hidden> wrote:

Yes I understand a minimal example is ideal, but I don't think this would occur with minimal code. I'll run a couple of tests to check.

Chris

On 9 Jan 2016 4:33 am, "Abraham Lee" <address@hidden> wrote:
Chris,

Sorry, I didn't mean to have you send _me_ your code (typing error). Is your code that big that you can't reduce it down towards a "tiny example"? If you can, that'd be best. Otherwise, if a single file, just attach the file to an email. If a group of files, then a .zip folder would be fine. I've seen others share code via gist or github, etc. Take your pick I guess.

Best,
Abraham

On Friday, January 8, 2016, Chris Yate <address@hidden> wrote:

Hi, and thanks. 

How would be best to give you the code? I could attach as a .zip to a list email, or upload to a gist.

(Please note, I'm using openlilylib, minimally, which I doubt has anything to do with the bug but is a dependency)

Forwarding to the bug list. Yes, if I'd make your code available to the developers. 

Best,
Abraham

---------- Forwarded message ----------
From: Chris Yate <address@hidden>
Date: Friday, January 8, 2016
Subject: Manual page breaking causing assertion failure
To: Lilypond-User Mailing List <address@hidden>


Hi, 
I'm trying to paginate my score nicely and the automatic paging isn't good enough. So I'm doing all the page breaks manually -- and a certain situation is causing an assertion failure on compilation:

<< Snippet of output:

....

MIDI output to `BeiMannernScore.mid'...

Finding the ideal number of pages...

Fitting music on 9 or 10 pages...

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

Assertion failed!

Program: C:\Program Files (x86)\LilyPond\usr\bin\lilypond.exe

File: /home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-breaking.cc, Line 1180

_expression_: ret <= cached_line_details_.size ()

Exited with return code 3.

>>


The problem occurs with the page break on a specific bar. For now I've done the obvious thing and gone with a working state -- it's not critical.


Happy to push the code up to a Gist for anyone that wishes to debug the issue. Let me know.


(This is apparently not happening if I build on Linux, only in Windows).


Chris



Attachment: AssertionFailing.ly
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]