Segmentation fault with empty POSCAR
Posted: Wed Aug 10, 2016 10:56 pm
VASP 5.4.1 crashes with a segmentation fault if the POSCAR file is empty. Normally this would be obvious, but sometimes VASP writes an empty CONTCAR, and a job continuation script then overwrites the POSCAR with the empty file. A proper message to the user would be very helpful, especially since OUTCAR misleadingly ends with this line:
INCAR:
INCAR: