This topic helps you troubleshoot problems you might experience with C/C++test.

General

What files are analyzed? How do I analyze header files?

C/C++test analyzes C/C++ source files directly and header files indirectly. Based on the current selection, C/C++test will analyze all C/C++ source files and report violations for all source and header files from the selection (only for header files included by the source files).

For example:

• if the project root is selected, then all source files (and header files indirectly) will be analyzed.
• if a single source file is selected, then only that file will be analyzed (no header files will be analyzed).
• if single source file and a single header file is selected, then the source file (and header file if it's included by the source) will be analyzed.
• if only a header file is selected, then C/C++test will skip the analysis (header files are not analyzed directly).

How can I  modify the verbosity level of the C/C++test console?

Choose Parasoft> Preferences, select  Console, then select the desired verbosity level (High, Normal, Low).

What do I do if C/C++test runs out of memory?

To prevent C/C++test  from running out of memory, add memory parameters to the script or shortcut you are using to start C/C++test. The two parameters are the initial size of the JVM (Xms) and the maximum size of the JVM (Xmx). Typically, both are set to the same size (for instance, 1024MB). However, if you have occasional problems but don't want to always allocate a large amount of memory, you can set the parameters to different sizes (for example, 1024MB as the initial size and 1400MB for the maximum size). The maximum size you can set depends on your OS and JVM.

Examples:

C/C++test standalone: cpptest.exe -J-Xms1024m -J-Xmx1400m

C/C++test plugin for Eclipse: eclipse.exe -vmargs -Xmx1400m

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?.

How can I adjust connection timeouts?

If you suspect that your problems stem from network or connection problems, you may want to try adjusting timeouts by adding the following switches to your JVM:

If only parasoft.ws.timeout is set, it affects both socket and connection timeout.

If I’m having problems, what information should I send to the  C/C++test support team?

See Preparing a Support Archive.

Installation

How can I tell what version of C/C++test is installed?

To check which version of C++test is currently installed:

1. Choose Help> About Eclipse (for the plugin) or Help> About Parasoft C/C++test (for the standalone version).
2. Click the Parasoft button. The About Features dialog will open.
3. Check the C/C++test version in the features table (the Version column).

What if C/C++test was not (re-) installed correctly?

Try to launch Eclipse (once) with the -clean option. This will force a refresh of an internal (Eclipse) registry/cache.

Why does Eclipse crash upon startup now that I installed the C/C++test plugin?

Eclipse may crash when it cannot write to the location in the installation directory where configuration files are kept. This is common when Eclipse is set up to have multiple users share a single install area. To prevent this, store config files in your home directory. See Requirements and Multi-user Installations.

How can I prevent my machine ID from floating?

Changes in the network environment may affect the interface that is used to compute your machine ID and result in machine ID instability. You can use the PARASOFT_SUPPORT_NET_INTERFACES environment variable to specify a stable interface and prevent the machine ID from floating.

1. Set up the PARASOFT_SUPPORT_NET_INTERFACES environment variable.

2. Set the variable value to a stable Ethernet network interface. Do not use virtual, temporary or loopback interfaces. 
   - On Windows: Set the value to the MAC address of your network card. You can use the ipconfig -all command to obtain the address.  For example:

   SET PARASOFT_SUPPORT_NET_INTERFACES=00-10-D9-27-AC-85

   - On Linux: Set the value to one of the network interfaces from the "inet" or "inet6" family. You can use the ifconfig command to obtain the list of available interfaces. For example: 

   export PARASOFT_SUPPORT_NET_INTERFACES=eth1

If the problem persists, you can obtain diagnostic information by setting up the environment variable PARASOFT_DEBUG_NET_INTERFACES and setting its value to true. This will print to the standard output the checking procedure that can be shared with technical support, as well as the interface that is used to compute your machine ID. The interface will be marked with the [SELECTED] prefix.

What if my Machine ID is WIN32-0?

If your Machine ID is WIN32-0, remove the license file located in <DRIVE>:\Users\<USER_NAME>\.parasoft\C++test\10.x\license.

Why are suppressions of some rules no longer available on DTP after C/C++test was upgraded to a newer version?

Suppressions associated with rules whose messages changed between releases may not be available on DTP and the rules must be re-suppressed.

You can restore legacy messages for BD category rules in version 10.4.1 and later by configuring the following advanced option (see Configuring Advanced Options):

CPPTEST_ENGINE_EXTRA_ARGS="-property flowanalysis.legacy.messages.for.<rule_ID>=true"

For example:

CPPTEST_ENGINE_EXTRA_ARGS="-property flowanalysis.legacy.messages.for.BD.PB.ARRAY=true -property flowanalysis.legacy.messages.for.BD.PB.ZERO=true"

To successfully restore the legacy messages, ensure that you remove the .cpptest folder that contains the local C/C++test cache data from following location: <workspace_location>/.cpptest/.dtpengine/.cpptest.

Testing and Analysis

What if the compiler family is not auto-detected?

Ensure that you have correctly configured your environment for the given compiler before launching Eclipse (including. $PATH, $LD_LIBRARY_PATH etc.)

What if C/C++test is unable to preprocess source files with a QNX compiler configuration?

QNX GCC compilers may prevent C/C++test from working properly if C/C++test is installed in a directory with a space its name (for example, C:\Program Files).

If you want to use C/C++test with a QNX compiler, ensure that the name of C/C++test installation directory does not have a space.

How do I work with Microsoft Visual C++ compilers?

Visual C++ 6.0

Import the project as described in To create a C++test project from a Visual Studio 6.0 project:

Other Versions of Visual C++

For other versions of Microsoft Visual C++, use the "Visual Studio Command Prompt" utility script (provided with the Visual Studio installation) to open a console with the Visual Studio environment. Then, launch Eclipse from that console to ensure that the environment is correctly configured. Note that C++test is also available as a plugin for Visual Studio 2005 and newer versions.

Is it possible to create a project using command-line utility (cpptestcli)?

You can create a project using cpptestcli. See Creating a Project Using an Existing Build System.

What if C/C++test is unable to execute test cases with the Debug Unit Tests test configuration?

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 a timeout during static analysis?

To ensure the analysis completes, you can do one of the following:

• 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 one or more files were not found when collecting static coverage data?

The setup problem that specifies the file (or files) that was not found when collecting static coverage data indicates that the local path of the file is different from its build-time path.

As a workaround, you can use the CPPTEST_COVERAGE_SRC_ROOT environment variable to map the original path to the local path:

CPPTEST_COVERAGE_SRC_ROOT=original/path1=local/path1;original/path2=local/path2;...

Reports

How can I create a report with a list of active coding standard rules?

When generating a report, specify a report configuration file that contains the following entry:

results.report.active_rules=true

What if some characters fail to be properly displayed in C/C++test reports?

Reports generated by Parasoft products require a sans-serif font to be available in your environment. If your report fails to correctly display some characters, such as national characters, ensure that a sans-serif font is installed on your system.

What if C/C++test runs out of memory when generating the report?

C/C++test uses a separate JVM to generate reports after code is tested. You can increase the amount of memory allocated for generating C/C++test reports by configuring the parasoft.report.separate_vm.xmx system property, for example:

parasoft.report.separate_vm.xmx=1280m

You can configure the JVM that generates reports to use Java with a larger maximum memory size by setting the parasoft.report.separate_vm.java_home system property, for example:

parasoft.report.separate_vm.java_home=C:/Program Files/Java/jdk-12.0.1

Working in the IDE

What if the Parasoft menu is not available?

Set C/C++ or C++test as the current perspective (by choosing Window> Open Perspective> Other, then choosing C/C++ or C++test from the dialog that opens).

What if an overlay scrollbar in Eclipse hides some C/C++test's GUI elements on Linux?

Due to a bug in some Eclipse versions, an overlay scrollbar may partially hide the last item in a list or tree, preventing the user from clicking the item. As a workaround on Linux, you can disable overlay scrollbars by setting the following system variable: GTK_OVERLAY_SCROLLING=0

What if Eclipse reports syntax errors on code that is correct in test suites generated with C/C++test?

Eclipse may mark correct code elements in test suites with a red underline to indicate potential errors when Eclipse's CDT indexer is unable to recognize C/C++test-specific syntax. To prevent this, you can enable the Parasoft C/C+test Include Paths provider in the project properties:

1. Go to  C/C+ General> Preprocessor Include Paths, Macros etc.
2. Open the Providers tab.
3. Enable the Parasoft C/C+test Include Paths provider.

This workaround is only available for CDT-managed projects.