File lock error

SYMPTOMS

One or more of the errors and warnings below occur when you build with instrumentation.

filename: warning: EDEADLK reported, waiting and retrying
filename: File lock error: No locks available
filename: File lock error: Resource deadlock avoided

CAUSE

The file system containing the filename in the error message has a problem with file locking, or does not support file locking at all. Typical implementations of the Network File System (NFS) protocol are known to suffer weakness with file locking.

RESOLUTION

Relocate the file named in the error to a local file system.

If the error occurs with the coverage file, modify your COVFILE setting.

If the error occurs on a file in the .BullseyeCoverage directory, set the COVAPPDATADIR environment variable to a writable directory on the local file system where BullseyeCoverage can store information.

Updated: 23 Feb 2018