Andrew Bernard <[email protected]> writes:
> Thanks. Do we raise a bug? The program stops and will not continue to
> compile after this error.
Like after any failed assertion since an assertion indicates that the
program cannot continue sensibly.
So yes, that's a bug. The proper fix is finding out under which
conditions the assertion failure can trigger and then figure out how to
proceed in this case or how to avoid it.
The bandaid fix would be replacing the assertion failure with a
programming error as long as one can state with confidence that it will
not result in a hard crash.
--
David Kastrup
---
** [issues:#4864] using beamed groups across staves - adding a slur or a
phrasing slur causes lilypond to fail with an assertion**
**Status:** New
**Created:** Fri May 27, 2016 09:25 AM UTC by pkx166h
**Last Updated:** Fri May 27, 2016 09:27 AM UTC
**Owner:** nobody
On 26/05/16 10:52, Andrew Bernard wrote:
> I keep finding situations using beamed groups across staves where
> adding a slur or a phrasing slur causes lilypond to fail with the
> following error:
\version "2.19.41"
treble = {
\clef treble
\time 1/4
s4 s
}
bass = {
\clef bass
\time 1/4
%\once \override Beam.positions = #'(4 . 4)
\stemUp
c32[\( c
\change Staff = treble
\stemDown c' e' g' c'' c'
\change Staff = bass
\tuplet 5/4 { e c g, d32\rest e' }
\change Staff = treble
g'
\change Staff = bass
g
\change Staff = treble
a'']\)
}
\score {
\new PianoStaff
<<
\new Staff = "treble" { \treble }
\new Staff = "bass" { \bass }
>>
\layout {
}
}
>
> Processing `/home/andro/work/lilypond/fp/exp-slur-crash.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> /home/andro/work/lilypond/fp/exp-slur-crash.ly:15:6: warning: no
> viable initial configuration found: may not find good beam slope
> c32
> [\( c
> lilypond:
> /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227:
> T Interval_t::center() const [with T = double]: Assertion `!is_empty
> ()' failed.
>
> Refer to the MWE here for an example. This occurs in 2.19.41 at least.
> I have not tried previous versions.
>
> In other scenarios in my score even when the warning about not finding
> a good beam slope is not emitted I still get the crash reliably in
> this type of situation.
>
> Is this a bug?
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
