lilypond-devel
[Top][All Lists]
Advanced

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

Re: issue 1464 (was: a plea to new contributors)


From: Matthias Kilian
Subject: Re: issue 1464 (was: a plea to new contributors)
Date: Sun, 2 Jan 2011 12:35:28 +0100
User-agent: Mutt/1.4.2.3i

On Sun, Jan 02, 2011 at 08:39:03AM +0700, Joe Neeman wrote:
> > I tried the diff below, which `fixed' the segfault, but it may be
> > completely wrong (I'm currently not familiar with the LilyPond code
> > at all). Unfortunately, I don't have a new enough ImageMagick on my
> > system, so I can't run the regression tests.
> >
> > diff --git a/lily/metronome-engraver.cc b/lily/metronome-engraver.cc
> > index 0a41fc9..e34c0ad 100644
> > --- a/lily/metronome-engraver.cc
> > +++ b/lily/metronome-engraver.cc
> > @@ -95,7 +95,10 @@ Metronome_mark_engraver::acknowledge_break_aligned
> > (Grob_info info)
> >           && safe_is_member (g->get_property ("break-align-symbol"),
> >                              text_->get_property ("break-align-symbols"))
> >           && Item::break_visible (g))
> > -    support_ = g;
> > +    {
> > +      support_ = g;
> > +      text_->set_parent (g, X_AXIS);
> > +    }
> >  }
> >
> 
> In your original backtrace, is the X_AXIS parent of the Item in frame #2
> 0x0? If so, I'm fine with the patch.

You mean the g in line 197 of axis-group-interface.cc?

        Interval_t<int> rank_span = g->spanned_rank_interval ();

No, it's not 0x0.

Ciao,
        Kili



reply via email to

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