Dear Aaron,

To be honest, I haven't got the fogiest.

On other architectures, it works fine. And test5 hasn't been individually
changed since v1.8 was released (24 Aug 2016):

Could it be that it was an individual accidental seg fault, which doesn't
re-occur upon running another time?

Best wishes,

Reply via email to