On 9/6/17, Natalie Silvanovich <[hidden email]> wrote:
> I'm experiencing a crash when loading a database with a corrupt journal
The chances of hitting the problem by accident are remote - so much so
that it is impossible in practice. This problem can only come up if
an adversary deliberately crafts a malicious rollback journal and
tricks an application into using it.
In any event, the problem is now fixed on trunk. Thanks for the
concise and clear bug report!