bug-lilypond
[Top][All Lists]
Advanced

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

Re: hidenotes bug


From: Erik Sandberg
Subject: Re: hidenotes bug
Date: Wed, 19 Jan 2005 11:52:00 +0100
User-agent: KMail/1.7.1

On Tuesday 18 January 2005 05.42, Graham Percival wrote:
> On 16-Jan-05, at 4:19 PM, Erik Sandberg wrote:
> >> (LilyPond chokes with an "abort trap" message; 2.4.2 on OSX)
> >
> > I can't reproduce - It never crashes here, neither with Pedro's 2.4.2
> > debian
> > package nor with 2.4.3 from CVS.
> >
> > Could you send the lilypond --verbose output?
>
> Umm.  Kind-of.  You're not going to believe this, but it works fine when
> I call it with --verbose.
>
> ending of output of "lilypond bar.ly":
> ----
> bar.ly:30:27: warning: Can't have rests and note heads together on a
> stem.:
>   <<{ c8\noBeam (\hideNotes
>                             c)}{s8 r}>>\unHideNotes
>
> bar.ly:31:28: warning: Can't have rests and note heads together on a
> stem.:
>    <<{ c8\noBeam (\hideNotes
>                              c)}{s8 r}>>\unHideNotes
> [4]
> Preprocessing graphical objects...
> Calculating line breaks... [3][4]
> Abort trap
> ----
>
> same portion of the output of "lilypond --verbose bar.ly":
> ----
>
> bar.ly:31:28: warning: Can't have rests and note heads together on a
> stem.:
>    <<{ c8\noBeam (\hideNotes
>                              c)}{s8 r}>>\unHideNotes
> [4]elapsed time: 0.22 seconds
> Element count 220 (spanners 19) Preprocessing graphical objects... Grob
> count 310[/sw/share/lilypond/2.4.2/f
> onts/afm/feta11.afm][/sw/share/lilypond/2.4.2/fonts/tfm/feta11.tfm][/
> sw/share/lilypond/2.4.2/fonts/afm/parme
> san11.afm][/sw/share/lilypond/2.4.2/fonts/tfm/parmesan11.tfm[/sw/share/
> lilypond/2.4.2/ps/parmesan20.enc]][/s
> w/share/lilypond/2.4.2/fonts/afm/feta13.afm][/sw/share/lilypond/2.4.2/
> fonts/tfm/feta13.tfm][/sw/share/lilypo
> nd/2.4.2/fonts/afm/parmesan13.afm][/sw/share/lilypond/2.4.2/fonts/tfm/
> parmesan13.tfm][/sw/share/lilypond/2.4
> .2/fonts/afm/feta14.afm][/sw/share/lilypond/2.4.2/fonts/tfm/
> feta14.tfm][/sw/share/lilypond/2.4.2/fonts/afm/p
> armesan14.afm][/sw/share/lilypond/2.4.2/fonts/tfm/parmesan14.tfm][/sw/
> share/lilypond/2.4.2/fonts/afm/feta16.
> afm][/sw/share/lilypond/2.4.2/fonts/tfm/feta16.tfm][/sw/share/lilypond/
> 2.4.2/fonts/afm/parmesan16.afm][/sw/s
> hare/lilypond/2.4.2/fonts/tfm/parmesan16.tfm][/sw/share/lilypond/2.4.2/
> fonts/afm/feta18.afm][/sw/share/lilyp
> ond/2.4.2/fonts/tfm/feta18.tfm][/sw/share/lilypond/2.4.2/fonts/afm/
> parmesan18.afm][/sw/share/lilypond/2.4.2/
> fonts/tfm/parmesan18.tfm][/sw/share/lilypond/2.4.2/fonts/afm/
> parmesan20.afm][/sw/share/lilypond/2.4.2/fonts/
> tfm/parmesan20.tfm][/sw/share/lilypond/2.4.2/fonts/afm/feta23.afm][/sw/
> share/lilypond/2.4.2/fonts/tfm/feta23
> .tfm][/sw/share/lilypond/2.4.2/fonts/afm/parmesan23.afm][/sw/share/
> lilypond/2.4.2/fonts/tfm/parmesan23.tfm]
> Calculating line breaks... Global shortest duration is 1/8
> [3][4]
> Optimal demerits: 32.877802
> Element count
> 111.[0][[/sw/share/texmf-local/fonts/tfm/public/ec-fonts-mftraced/
> ecrm6.tfm[/sw/share/texmf/dv
> ips/base/tex256.enc]][/sw/share/texmf-local/fonts/tfm/public/ec-fonts-
> mftraced/ecrm8.tfm][/sw/share/lilypond
> /2.4.2/tex/latin1.enc]1][2][/sw/share/texmf-local/fonts/tfm/public/ec-
> fonts-mftraced/ecbx6.tfm][/sw/share/te
> xmf-local/fonts/tfm/public/ec-fonts-mftraced/ecbx8.tfm][/sw/share/
> texmf-local/fonts/tfm/public/ec-fonts-mftr
> aced/ecbx10.tfm][/sw/share/texmf-local/fonts/tfm/public/ec-fonts-
> mftraced/ecbx12.tfm][/sw/share/texmf-local/
> fonts/tfm/public/ec-fonts-mftraced/ecrm10.tfm][/sw/share/texmf-local/
> fonts/tfm/public/ec-fonts-mftraced/ecrm
> 17.tfm]Layout output to `bar.tex'...
> This is TeX, Version 3.14159 (Web2C 7.4.5)
> LaTeX2e <2001/06/01>
> ---- (continues, all looks good)
>
> I doubted my sanity, so I tried it without --verbose again.  Still
> gives the
> "Abort trap" message.
>
> Since this bug seems fairly esoteric -- a fairly contrived input
> example, not
> always manifesting -- I vote that we not worry about it.  Maybe it's
> some weird
> fink / OSX flaw in some underlying library that won't apply to the new
> fink
> stuff for 2.5.x.  :)

OK, we'll ignore that problem for now, just be sure to report if it starts 
happening again.

Erik




reply via email to

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