Actually, I get
~~~
#0  Grob::internal_get_property_data(scm_unused_struct*) const 
(sym=0x7ffff62d9a60, this=0x0) at grob-property.cc:140
#1  Grob::internal_get_property(scm_unused_struct*) const (this=this@entry=0x0, 
sym=0x7ffff62d9a60) at grob-property.cc:162
#2  0x0000555555744192 in Staff_symbol::line_positions(Grob*) (me=0x0) at 
staff-symbol.cc:113
#3  0x000055555583c1f3 in Multi_measure_rest::church_rest(Grob*, Font_metric*, 
int, int, double) (me=me@entry=0x555555e2a560, 
musfont=musfont@entry=0x555555e20e00, measure_count=measure_count@entry=1, 
mdl=<optimized out>, space=space@entry=0) at multi-measure-rest.cc:268
#4  0x000055555583cc3d in Multi_measure_rest::symbol_stencil(Grob*, double) 
(me=me@entry=0x555555e2a560, space=space@entry=0) at multi-measure-rest.cc:216
#5  0x000055555583d643 in 
Multi_measure_rest::set_spacing_rods(scm_unused_struct*) (smob=<optimized out>) 
at multi-measure-rest.cc:417
#6  0x00007ffff7db3d82 in scm_dapply (proc=0x7ffff6be1ea0, arg1=0x7ffff375b9a0, 
args=0x404) at eval.c:4895
#7  0x0000555555655df9 in Grob::try_callback_on_alist(scm_unused_struct**, 
scm_unused_struct*, scm_unused_struct*) (this=this@entry=0x555555e2a560, 
alist=alist@entry=0x555555e2a5e8, sym=sym@entry=0x7ffff62cb080, 
proc=proc@entry=0x7ffff6be1ea0) at 
/usr/local/tmp/lilypond/lily/include/smobs.hh:318
#8  0x00005555556561c7 in Grob::internal_get_property(scm_unused_struct*) const 
(this=this@entry=0x555555e2a560, sym=0x7ffff62cb080) at grob-property.cc:184
#9  0x00005555555fef53 in System::pre_processing() (this=0x555555e20b80) at 
system.cc:552
#10 0x0000555555815579 in Paper_score::process() (this=0x555555d07170) at 
paper-score.cc:136
~~~
which should be about enough to track this down.

Thanks!


---

** [issues:#5964] Multi_measure_rest_engraver segfaults when its context 
doesn’t include Staff_symbol_engraver.**

**Status:** Accepted
**Labels:** Regression 
**Created:** Wed May 06, 2020 10:47 PM UTC by Valentin Villenave
**Last Updated:** Wed May 06, 2020 10:59 PM UTC
**Owner:** nobody


This used to work as recently as 2.20.0, and it no longer does:
~~~~
\version 2.21.1
\layout {
  \context {
    \type Engraver_group
    \name GlobalRests
    %\consists Staff_symbol_engraver
    %\omit StaffSymbol
    \consists Multi_measure_rest_engraver
  }
  \context {
    \Score
    \accepts GlobalRests
  }
}
\score {
    \new GlobalRests { R1 }
}
~~~~
Uncommenting the Staff_symbol_engraver prevents the segfault from happening.
Here’s what gdb has to say:
~~~
Program received signal SIGSEGV, Segmentation fault.
Grob::internal_get_property (this=this@entry=0x0, sym=0x7fffe98e1ea0) at 
grob-property.cc:162
162       SCM val = get_property_data (this, sym);
~~~
Reported by Trevor B: 
https://lists.gnu.org/archive/html/lilypond-user/2020-05/msg00077.html


---

Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net 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.
_______________________________________________
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to