Looks like the routine that prints the error message was written to be run when the file is being processed, so it is making assumptions about which file is under consideration. It should be easy enough to fix.