Page History

...

eclipse.exe -vmargs -Xmx1400m

You can also customize the amount of allocated memory with the CPPTEST_ENGINE_EXTRA_ARGS option by specifying the value of the -Xmx setting. This may be particularly useful for when you perform static analysis or report results to DTP. See Configuring Advanced Options for details.

If C/C++test runs out of memory when generating the report, see What if C/C++test runs out of memory when generating the report?.

...

If you debug code compiled with the Microsoft Visual C++ 14.2 compiler shipped with Visual Studio 2019, launch Visual Studio 2019 IDE prior to debugging and ensure it is running in the background until the C/C++test run has ended.

What can I do if C/C++test reports test reports a timeout during static analysis?

...

• Increase the timeout limit by configuring the following advanced option:
  cpptest.analyzer.source.timeout=<TIMEOUT_IN_SECONDS> 
  See Configuring Advanced Options.

• Disable the most time-consuming rules or metrics in your test configuration. The information about the times is included in the timeout message displayed on the console and in the report.
• Contact Parasoft Support.

What if C/C++test fails to run static analysis when the workspace path is too long?

If the workspace path exceeds 126 characters, C/C++test may create internal paths that exceed the Windows maximum path length. The exact path length can vary because some directory names are generated dynamically. In such cases, the C/C++test engine may be unable to access internal files such as xtest.dll and read the license configuration. As a result, C/C++test will be unable to obtain a license and run static analysis.

To resolve this issue, use one or both of the following approaches:

1. Move the C/C++test workspace to a directory closer to the drive root to reduce the total path length.

2. Specify a fixed location for Parasoft local storage by setting the parasoft.local.storage.dir property using one of the following methods:

   • As an environment variable:

     Code Block
     CPPTEST_ENGINE_EXTRA_ARGS="-J-Dparasoft.local.storage.dir=C:\temp\workspace\.cpptest"

   • As a cpptestcli command-line parameter:

     Code Block
     -J-DCPPTEST_ENGINE_EXTRA_ARGS="-J-Dparasoft.local.storage.dir=C:\temp\workspace\.cpptest"

   • As a Java argument in the <cpptest_dir>\bin\cli\etc\cpptestcli.jvm file:

     Code Block
     -Dparasoft.local.storage.dir=C:/temp/workspace/.cpptest

   • In the IDE, as a technical support advanced option set for a specific workspace (see Configuring Advanced Options): 

     Code Block
     CPPTEST_ENGINE_EXTRA_ARGS="-J-Dparasoft.local.storage.dir=C:/temp/workspace/.cpptest"

What if one or more files were not found when collecting static coverage data?

...