Docker: Aborting an initial stack exec can turn all futher stack execs into segfaults #2568
When using stack with docker, I ran and then pressed Ctrl-C:
Following this, all my
This is on stack-1.2.2 on Ubuntu 16.04.
I think the fix for this would be to always check that files stack puts into place are still there with the right file size, which guards against premature copy aborts with Ctrl-C or computer crashes (and is much faster than hashing the file contents, which would add a recurring startup overhead).
The text was updated successfully, but these errors were encountered: