This topic helps you troubleshoot problems you might experience with C++test.
To check which version of C++test is currently installed:
Because 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 (for details on how to do this, see the first bullet in Other Requirements).
Try to launch Eclipse (once) with the
-clean option. This will force a refresh of an internal (Eclipse) registry/cache.
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).
Ensure that you have correctly configured your environment for the given compiler before launching Eclipse (including. $PATH, $LD_LIBRARY_PATH etc.)
Import the project as described in To create a C++test project from a Visual Studio 6.0 project:
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.
To prevent C++test from running out of memory, add memory parameters to the script or shortcut being used to start 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.
cpptest.exe -J-Xms1024m -J-Xmx1400m
C++test plugin for Eclipse:
eclipse.exe -vmargs -Xmx1400m
-Xmxsetting. This may be particularly useful for when you perform static analysis or report results to DTP. See Configuring Advanced Options for details.
C++test analyzes C/C++ source files directly and header files indirectly. Based on the current selection, 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).
.pathtoeclipse file is automatically created when you install C++test with the
extinstall utility. This file contains the location of your Eclipse installation. If the file is missing (as indicated by the above message), manually add it by creating a simple text file, adding a line with your Eclipse location, then saving it as
Yes. See Creating a Project Using an Existing Build System.
When generating a report, specify a report configuration file that contains the following entry:
Choose Parasoft> Preferences, select Console, then select the desired verbosity level (High, Normal, Low).
|High Verbosity||Normal Verbosity||Low Verbosity|
Basic info about the current step’s name and status (done, failed, up-to-date)
|Violations printed out during static analysis and unit testing execution|
See Migrating test assets from C++test 6.x.
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.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:
See Contacting Parasoft Technical Support.