Description of problem: lilypond segfaults on Fedora 24 and gcc 6 with some input files. Version-Release number of selected component (if applicable): lilypond-2.19.45-1.fc24.x86_64 How reproducible: Render a particular complex score (not really clear what input triggers the crash) Steps to Reproduce: 1. Run lilypond a_score_file.ly Actual results: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000055d912666faf in Grob::get_offset (this=this@entry=0x0, a=a@entry=X_AXIS) at grob.cc:400 400 if (dim_cache_[a].offset_) Expected results: The score compiles and the pdf is generated Additional info: This is probably due to this recent gcc 6 new optimization: Optimizations remove null pointer checks for this The backtrace shows that the crash is in grob.cc: #0 0x000055d912666faf in Grob::get_offset(Axis) const (this=this@entry=0x0, a=a@entry=X_AXIS) at grob.cc:400 #1 0x000055d9126670a8 in Grob::relative_coordinate(Grob const*, Axis) const (this=0x0, refp=0x55d914f179f0, a=X_AXIS) at grob.cc:341 #2 0x000055d9126670ce in Grob::relative_coordinate(Grob const*, Axis) const (this=0x55d914ee8600, refp=0x55d914f179f0, a=X_AXIS) at grob.cc:345 #3 0x000055d9126670ce in Grob::relative_coordinate(Grob const*, Axis) const (this=0x55d914936920, refp=0x55d914f179f0, a=X_AXIS) at grob.cc:345 #4 0x000055d9126670ce in Grob::relative_coordinate(Grob const*, Axis) const (this=0x55d9149371c0, refp=0x55d914f179f0, a=X_AXIS) at grob.cc:345 #5 0x000055d9126670ce in Grob::relative_coordinate(Grob const*, Axis) const (this=0x55d914936c40, refp=0x55d914f179f0, a=X_AXIS) at grob.cc:345 #6 0x000055d9126670ce in Grob::relative_coordinate(Grob const*, Axis) const (this=this@entry=0x55d914937360, refp=0x55d914f179f0, a=a@entry=X_AXIS) at grob.cc:345 #7 0x000055d9123bc194 in Slur_configuration::score_extra_encompass(Slur_score_state const&) (this=0x55d914de9fb0, state=...) at slur-configuration.cc:341 #8 0x000055d9123bcae5 in Slur_configuration::run_next_scorer(Slur_score_state const&) (this=0x55d914de9fb0, state=...) at slur-configuration.cc:522 #9 0x000055d9125088ab in Slur_score_state::get_best_curve() const (this=this@entry=0x7fffad986a00) at slur-scoring.cc:427 #10 0x000055d912508b0f in Slur::calc_control_points(scm_unused_struct*) (smob=<optimized out>) at slur-scoring.cc:363 #11 0x00007fcaaf894cf5 in scm_dapply () at /lib64/libguile.so.17 I made a patch that seems to solve this problem and a second one to solve a FTBFS problem with 'constexpr' needed for in-class initialization of static data member. I'll attach them here
Created attachment 1182861 [details] Patch to solve crash
Created attachment 1182862 [details] Patch to solve FTBFS with gcc 6
*** Bug 1359213 has been marked as a duplicate of this bug. ***
The crash patch applies, but the FTBFS patch doesn't, as it looks like it was derived from code other than 2.19.45. Can you double-check?
Sorry, the second patch is against lilypond current git master branch (commit 445bf3bb2fbd1f2), that problem is not present in version 2.19.45. Please do not apply the second patch to version 2.19.45, maybe it will be useful for the next version.
I wondered if that might be the case. Thanks, I'll get the first patch out ASAP.
lilypond-2.19.45-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d34b2bff27
These 2 issues have been corrected upstream too, version 2.19.46 will contain the fixes.
lilypond-2.19.45-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d34b2bff27
Excellent, thank you!
lilypond-doc-2.19.46-1.fc24 lilypond-2.19.46-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7937127a2d
Checks out OK for me!
lilypond-2.19.46-2.fc24, lilypond-doc-2.19.46-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7937127a2d
lilypond-2.19.46-2.fc24, lilypond-doc-2.19.46-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.