[Top][All Lists]

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

Re: How to debug std::bad_alloc

From: Keith OHara
Subject: Re: How to debug std::bad_alloc
Date: Fri, 14 Jun 2013 01:48:22 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Jean-Charles Malahieude <lilyfan <at> orange.fr> writes:

> terminate called after throwing an instance of 'std::bad_alloc'
>    what():  St9bad_alloc
> I think I've narrowed the problem to a particular score which, when 
> alone, compile fine.

LilyPond asks for more memory than your computer has.  The reason the
changes you describe would cause her to need more memory are not clear
to me. 

My only suggestion is to use \bookpart{} to divide the book into smaller
sections for page-breaking, and maybe use the "minimal" page breaking
method if you are not depending on LilyPond to choose the page breaks.

reply via email to

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