Re: LilyPond crashes on \musicglyph #"space"

[BB]

I have tried both without crash on linux mint.

On 29.08.2015 16:17, Richard Shann wrote:
> Sorry all, I have
>
> lilypond --version
> GNU LilyPond 2.19.25
>
> so my file was misleading - I was using Frescobaldi and it said
>
> Starting lilypond 2.18.2 [test.ly]...
> Processing `/tmp/frescobaldi-lN9e5p/tmpJpi_kn/test.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...terminate called after throwing an
> instance of 'std::bad_alloc'
>    what():  std::bad_alloc
> Exited with exit status 1.
>
> I can only guess that Frescobaldi silently ran convert-ly so that the
> "Starting lilypond 2.18.2 ..." was misleading.
>
> I can confirm that all the other glyphs work (I am creating a
> cheat-sheet of all the glyphs so that Denemo users can pick one
> graphically ...)
>
> Richard
>
>
>
>
> On Sat, 2015-08-29 at 13:57 +0200, Thomas Morley wrote:
> > 2015-08-29 13:38 GMT+02:00 Richard Shann <address@hidden>:
> > > I just noticed that LilyPond is crashing on this:
> > >
> > > \version "2.18.0"
> > > {
> > > <> ^\markup {\musicglyph #"space"} s1*4/4
> > > }
> > >
> > > with
> > >
> > > Interpreting music...
> > >
> > > Preprocessing graphical objects...terminate called after throwing an
> > > instance of 'std::bad_alloc'
> > >
> > > what(): std::bad_alloc
> > >
> > > Exited with exit status 1.
> > >
> > > Other glyphs so far seem ok.
> > >
> > > Richard
> >
> >
> > Confirmed with released 2.19.25
> >
> > No problem with a build from lastest master with --disable-optimising
> >
> > Both on Linux
> >
> > Cheers,
> >    Harm
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user