> On Feb 21, 2020, at 6:20 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Looking at that thread, I don't really get the feeling that they're any
> more helpful now :/

I can second that thought. 

> As an alternative, maybe it'll be possible to build a new version of the
> 0.16 Hugo binary with a newer Go runtime? I very much doubt that the
> segfault is because of the Hugo code itself...

My thought exactly. In case anyone has a burning urge to get distracted on this, I'll take a whack at this over the weekend. (After all, it's my computer that's busted...)

Rich