Re: Manual page breaking causing assertion failure

[Abraham Lee]

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
> <javascript:_e(%7B%7D,'cvml','address@hidden');>>
> Date: Friday, January 8, 2016
> Subject: Manual page breaking causing assertion failure
> To: Lilypond-User Mailing List <address@hidden
> <javascript:_e(%7B%7D,'cvml','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
>
>