How to debug std::bad_alloc

2013-06-12 Thread Jean-Charles Malahieude 

Hi all,

I've typeset BWV246 and printed an Urtext version without any problem.
A modern version spits me (version 2.17.20)

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.


I need some help in order to understand what's going wrong.

The only differences are:

- using \keepWithTag #'Full for modern
  as opposed to\keepWithTag #'(Full Urtext) for Urtext

- the global size

- some paper block variables
  inner-margin = 1.2\cm % for Urtext, 1cm
  outer-margin = 1.3\cm % for Urtext, 1cm
  binding-offset = 0.6\cm %for Urtext, 0.4cm
%  top-system-spacing #'basic-distance = #10 % for Urtext
%  top-markup-spacing #'basic-distance = #10 % for Urtext
%  last-bottom-spacing #'basic-distance = #10 % for Urtext

- nonstaff-unrelatedstaff-spacing
  minimum-distance at 2 in Urtext, 3 otherwise

- singers clefs

TIA,
JeanCharles


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: How to debug std::bad_alloc

2013-06-13 Thread Jean-Charles Malahieude 

Le 12/06/2013 20:45, Jean-Charles Malahieude disait :

Hi all,

I've typeset BWV246 and printed an Urtext version without any problem.
A modern version spits me (version 2.17.20)

terminate called after throwing an instance of 'std::bad_alloc'
   what():  St9bad_alloc



For anyone interested, a tarball of the sources is available on demand 
(87ko).


As soon as I add another score to number 42, I get this very message, 
and invoking with -l DEBUG is of no help for me.


TIA,
Jean-Charles


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: How to debug std::bad_alloc

2013-06-13 Thread Keith OHara 
Jean-Charles Malahieude  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.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond