In this section:

What's New

• New parser, C++17 is now fully supported
• Added support MSVC++-15.0 (VS 2015). See Requirements for additional information.
• MSVC++-10.0 (VS 2010) is no longer supported. See Requirements for additional information.

Known Issues

This section describes known issues in this release. This list is an addendum to known issues in previous releases.

All Platforms

C++11, C++14 and C++17 features are not compatible with object wrapping. Set the tempInitWrapping directive to off in your .psrc configuration by adding the Insure++tempInitWrapping off directive. In some instances this may also require the checkingUninitObject option to be set to off by adding the Insure++.checkingUninitObjects off directive.

Windows

Use of <typeinfo> constructs, (e.g., typeid(type).name()) causes heap corruption. The workaround is to turn off guardzones by adding the following directive to your .psrc file (Unix) or in the Advanced Options panel (Windows): 
Insure++.guardSize 0.

AutoCAD plugins are incompatible with Insure++. Consider using C++test with Flow Analysis.

Visual Studio 2012 and Later

The following known issues are specific to Visual Studio 2010 and later:

• Visual Studio does not use the VS Debug API when debugging managed executables. As a result debugging managed executables is not supported. This only applies to debugging--executing such applications is still supported.
• The Insure++ Build function does not rebuild anything when header files are changed. This issue is a Microsoft dependency tracking bug. The workaround is to use Instrument File, Insure++ Rebuild Selection, and/or Insure++ Rebuild Solution when necessary.
• When only the Visual C++ component is installed, the Insure++ toolbar is ineffective. The buttons will function after restarting Visual Studio, but the Tools->Insure++ menu will remain unavailable. .NET components must be installed for the toolbar and menu items to function.

Windows 7 and Windows Server 2008 R2 and Later

• Running Insure++ from Visual Studio without elevated privileges may result in INSURE_ERROR messages related to .gus files. The workaround is to run with elevated privileges once, to "prime" the cache.
• The Suppressions Panel will not work properly unless Insure++ is started with elevated privileges or the Enable user specific options option is enabled in the Insure++ Control Panel.
• Session zero isolation prevents user interaction with Insra when injecting system services. The workaround is to use a report file.

Windows x64

• On Windows 7 and Windows 10, you may see USER_ERROR messages for stack traces that do not include any user code. These messages are often due to undocumented aspects of Windows interfaces and may be safely ignored.
• C# executables built with /platform:anycpu (the default) fail to run under Insure++. The workaround is to build with either /platform:x86 or /platform:x64.

Additional Updates

• Machine ID generation has been updated to be consistent with other Parasoft tools.

PRs and FRs

The following PRs/FRs were addressed in this release: