Re: 2.17.6: assertion failed with \glissando

[Keith OHara]

On Tue, 20 Nov 2012 22:55:21 -0800, Werner LEMBERG <address@hidden> wrote:

> > > BTW, here is a full backtrace (of the first 32 frames).
> >
> > > #0  Interval_t<double>::center (this=0xbfff96ec)
> > >     at ../flower/include/interval.hh:226
> > > #1  0x082d9cdd in Note_head::get_stem_attachment (fm=0x8602ec8, key=...)
> > >     at note-head.cc:181
> >
> > Somehow, you got a misleading backtrace, because note-head.cc:180
> > tests the same condition as the assertion that you report as failed.
>
> Misleading?

That backtrace described a call to center() that would have succeeded, if it 
were allowed to continue.  (It looks like you stopped the program while 
LilyPond was setting the stem on the first of the two notes joined by the 
glissando.)  Thus, all the information in the backtrace pertains to a situation 
that does not lead to the problem.

> I've set the breakpoint directly at
> interval.hh:226.  What should I've done instead?

Let the assert fail, then backtrace after the program exits, or set a 
conditional breakpoint depending on the (negative of the) condition in the 
assert, if you debugger supports such a thing.