I was unable to replicate this issue on a Debian EC2 instance. However, there are very few things that happen between printing "End time:" and program exit, so I have added a bunch of debug-prints (active when the --debug flag is passed in) to the latest GitHub commit that should reveal which of those few things is triggering the segfault; let me know if you are able to run this build.
On Thu, Feb 17, 2022 at 11:47 AM Andreas Tille <andr...@an3as.eu> wrote: > Am Thu, Feb 17, 2022 at 11:39:30AM -0800 schrieb Chris Chang: > > Haven't yet replicated this on any of my usual non-Debian test machines, > > but I will spin up a Debian EC2 instance within the next two days and try > > to replicate the crash there. > > Thanks a lot, Andreas. > > -- > http://fam-tille.de >
