On Thu, Nov 22, 2012 at 11:46:07AM +, Ian Hulin wrote:
> Hi Colin, Keith and Walter,
> On 22/11/12 09:19, Colin Hall wrote:
> > On Wed, Nov 21, 2012 at 05:08:52AM +, Keith OHara wrote:
> >> The released builds are not compiled this way, so no-one can
> >> reproduce your bug without using Li
Hi Colin, Keith and Walter,
On 22/11/12 09:19, Colin Hall wrote:
> On Wed, Nov 21, 2012 at 05:08:52AM +, Keith OHara wrote:
>> Werner LEMBERG gnu.org> writes:
>>
>>> This time I tried with current git (commit 436824b8):
>>>
../flower/include/interval.hh:226: T Interval_t::center()
On Wed, Nov 21, 2012 at 05:08:52AM +, Keith OHara wrote:
> Werner LEMBERG gnu.org> writes:
>
> > This time I tried with current git (commit 436824b8):
> >
> > > ../flower/include/interval.hh:226:
> > > T Interval_t::center() const [with T = double]:
> > > Assertion `!is_empty ()' f
>> - y = me->get_bound (dir)->extent (common_y, Y_AXIS).center ();
>> + Interval ii = me->get_bound (dir)->extent (common_y, Y_AXIS);
>> + if (!ii.is_empty())
>> +y = ii.center ();
>
> This works, thanks, and I get output which looks like being
> predictable (see attached image), assuming
>> Misleading?
>
> That backtrace described a call to center() that would have
> succeeded, if it were allowed to continue.
Ah, yes, silly me.
> Let the assert fail, then backtrace after the program exits, or set
> a conditional breakpoint depending on the (negative of the)
> condition in the as
On Tue, 20 Nov 2012 22:55:21 -0800, Werner LEMBERG wrote:
BTW, here is a full backtrace (of the first 32 frames).
#0 Interval_t::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
>> I'm on a GNU/Linux box, running `autogen.sh' with
>> `--disable-optimising', and compiling with g++ 4.6.2.
>
> The released builds are not compiled this way, so no-one can
> reproduce your bug without using Linux to create a debug-enabled
> build.
Well, assertion aborts should *never* happen, s
Werner LEMBERG gnu.org> writes:
> This time I tried with current git (commit 436824b8):
>
> > ../flower/include/interval.hh:226:
> > T Interval_t::center() const [with T = double]:
> > Assertion `!is_empty ()' failed.
> I'm on a GNU/Linux box, running `autogen.sh' with
> `--disable-op
> ../flower/include/interval.hh:226:
> T Interval_t::center() const [with T = double]:
> Assertion `!is_empty ()' failed.
BTW, here is a full backtrace (of the first 32 frames).
Werner
==
#0 Interval_t::center (
This time I tried with current git (commit 436824b8):
>> \version "2.17.6"
>>
>> {
>> f2 \glissando
>> \override NoteHead #'stencil = ##f
>> e |
>> }
>>
>> causes the following output (beautified):
>
> no such messages wit 2.17.7 - but there is no glissando; use
> transpar
Eluze wrote
> use transparent instead.
or #'stencil = #point-stencil
which lets the ledger lines diappear
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/2-17-6-assertion-failed-with-glissando-tp136531p136613.html
Sent from the Bugs mailing list archive at Nabb
Werner LEMBERG wrote
> [commit 3bd44774]
>
> The following code
>
> \version "2.17.6"
>
> {
> f2 \glissando
> \override NoteHead #'stencil = ##f
> e |
> }
>
> causes the following output (beautified):
no such messages wit 2.17.7 - but there is no glissando; use transparent
[commit 3bd44774]
The following code
\version "2.17.6"
{
f2 \glissando
\override NoteHead #'stencil = ##f
e |
}
causes the following output (beautified):
GNU LilyPond 2.17.6
Processing `bug.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
13 matches
Mail list logo
