Knowledge Base > Legacy Information - JCover > Troubleshooting



Using the -- verbose option outputs a significant amount of extra information to the screen. This is often useful should troubleshooting be needed. Diffblue recommends running -- verbose on a single class in order to obtain more detailed output.

Linux Errors

If you see the following error message when running JCover:

jcover: error while loading shared libraries: cannot open shared object file: No such file or directory

then your JVM may be in a non-standard directory. To work around this issue, set the LD_LIBRARY_PATH environment variable to include the library’s location.

JDK 8 example:

$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/my_jdk_location/jre/lib/amd64/server

JDK 11 example:

$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/my_jdk_location/lib/server

Windows Errors

If your anti-virus software is configured to prevent unknown programs from running, they may be moved to a quarantine folder. When you try to run JCover (or any other unrecognized program) it may fail silently and be removed by the anti-virus software.

If this happens:

  1. Check your anti-virus software logs for messages relating to JCover.
  2. Ensure that JCover is added to the list of trusted programs.

macOS Errors

Unregistered apps

Opening an app which isn’t registered with Apple may lead to a warning. This can usually be resolved by following Apple’s advice on one of these support pages:

Timeout error

If you see the following error message when trying to run JCover:

execvp gtimeout failed: No such file or directory

then you need to install the coreutils package (which includes gtimeout), using either HomeBrew or Macports.