Control: forcemerge 871372 -1 On Tue, 27 Jun 2017, Thomas Wille wrote: > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead?
On Tue, 27 Jun 2017, Antonio Ospite wrote: > lilyopnd devs suggest[1] that this could be an issue with gcc-6, > reported in the issue 4814 on sf.net[2], which has been fixed by commit > b0dce76daf27 (Issue 4814: grob.cc segfaults with gcc6)[3]. Thanks for the report; I've confirmed that this is this issue, and I'm just about ready to roll out an update for it. -- Don Armstrong https://www.donarmstrong.com The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair. -- Douglas Adams _Mostly Harmless_
