• pfiles-name.conf
• pfiles-name.C.L.S.conf
  for all compiler C, language L, target address size S combinations used in the project
• pfiles-name.prj
• Directory pfiles-name.prj_files/
• pfiles-name.environ

There are several possibilities.

• If you have Bitdefender™ installed then the CodeSonar analysis will be unable to communicate with an HTTP hub, even if Bitdefender is disabled. (It will, however, be able to communicate with an HTTPS hub.)
• If you have Avast Antivirus installed then the spawncs process may become stuck, and may be difficult or impossible to kill. CodeSonar is not compatible with Avast Antivirus.
• [Windows only] CodeSonar may be waiting for services authentication. In this case, an authentication dialog will be open. (If you are working in other windows while running CodeSonar those windows might be obscuring the dialog: if you don't see a dialog, move the other windows to check underneath). See CodeSonar as a Windows Service for more information.
• If you are running CodeSonar from a continuous integration tool, ensure that all codesonar analyze invocations include either the -foreground option or the -wait option. Note that -foreground cannot be used with -remote analysis-launchd.
• If User Account Control is enabled, your system may be waiting for you to give permission for the analysis to run.

  

  Click Continue to proceed (you may also need to provide services authentication).

• disable build caching, and
• disable distributed building.

To resolve this, do the following.

1. Set VIRTUAL_COMPILER_PROXY=No in the project configuration file.
2. In your container, manually rename your compiler executables and then make a copy of our proxy (%CSONAR%\codesonar\bin\spawncs_userland.exe) where the compiler executable used to be.

   For a compiler executable named compilername.exe, the renamed file must be named compilername.orig.exe.

   For example:

   rename cl.exe cl.orig.exe
   copy "c:\Program Files\CodeSecure\CodeSonar\codesonar\bin\spawncs_userland.exe" cl.exe
   

For versions that have this problem, Symantec's recommended workaround is to uninstall the "Application and Device Control" component of Symantec Endpoint Protection:

1. Open the Control Panel.
2. Open the Programs and Features dialog.
   (Called Add/Remove Programs in older versions of Windows.)
3. Right click Symantec Endpoint Protection
4. Click Change.
   The Symantec Endpoint Protection installation wizard will open.
5. Click Next.
6. Select Modify and click Next.
7. Expand Proactive Threat Protection by clicking the + sign next to it.
8. Click the disk icon next to Application and Device Control.
9. Select Entire Feature will be unavailable.
10. Click Next as needed to effect the change.

If CodeSonar is configured to recognize your compiler compiler_name.exe and the build still does not seem to be recognizing the compilations:

• [Windows only] If you are building in an IDE, try restarting your build environment and then repeating all the build wizard steps.
• [Windows only] Otherwise, there may be issues with input/output redirection. To resolve this:
  1. Rename your native compiler executable compiler_name.exe to orig.compiler_name.exe.
     mv path\to\compiler_name.exe path\to\orig.compiler_name.exe
  2. Copy $CSONAR\gtr\bin\wrapper.exe to compiler_name.exe.
     cp $CSONAR\gtr\bin\wrapper.exe path\to\compiler_name.exe
  3. Build the project.
  4. Are the compiler invocations recognized?
     • YES: you do not need to do anything further.
     • NO: CodeSonar is not automatically recognizing the wrapped compiler calls. Go on to the next step.
  5. Add the following settings to your configuration file.

     COMPILER_MODELS += orig.compiler_name.exe -> model_to_use
     
     DISABLED_COMPILERS += compiler_name.exe
     

     where model_to_use.exe is the compiler model that corresponds to the compiler_name compiler.
  6. Build the project.
  7. Are the compiler invocations recognized now?
     • YES: you do not need to do anything further.
     • NO: contact CodeSecure support for assistance.
  The copy of wrapper.exe named compiler_name.exe will call orig.compiler_name.exe, so the behavior of your normal builds will not be affected.
• [Unix/Linux only] CodeSonar needs to know the environment variables that are active when the build is invoked in order to communicate those values to its subprocesses. Some build systems deliberately ignore these variables (e.g., the Scons build system). The file proj_name.environ contains a dump of all these environment variables. Set FORCE_ENVIRONMENT=Yes in the project configuration file to force CodeSonar to reset these variables to the values that are required.
• STk compiler models are no longer supported. If you have previously implemented a custom STk compiler model and need assistance converting it to C++ or Python, contact CodeSecure.

To resolve this, use front end option --pending_instantiations to set a higher bound on the number of instantiations of a given template that may be pending at a time. Try setting to 256 first, then increasing in powers of 2 until the parse error is resolved. If you reach 4096 without resolving the parse error, it is worth making sure that the code really should use such a deep instantiation stack before increasing further.

• No compilations have been performed. Build your software project, then click Finalize.
• Compilations have been performed but not recognized. Configure CodeSonar to recognize your compiler(s) using the instructions in section Mapping Compiler Names to Models.

To resolve:

1. Check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts, finding the entries for Courier, MS Serif and MS Sans Serif. There may be additional numbers in the font titles.
2. Change the settings for entries to COURE.FON, SERIFE.FON, and SSERIFE.FON, respectively.
3. Sign out of Windows, then sign back in.

• If your usual build command is based on something other than a .exe file, include "cmd /c" when constructing your CodeSonar build command. For example, if you usually build your project by invoking build.bat, your CodeSonar build command should be something like:
  codesonar analyze my-proj cmd /c build.bat
• If your usual build command is based on a .exe file name that represents a symbolic link, change it to refer to the actual windows file. For example, if you usually build your project by invoking python scons.py and /usr/bin/python.exe is actually a symbolic link to /usr/bin/python2.4.exe, your CodeSonar build command should be something like:
  codesonar analyze my-proj python2.4.exe scons.py

To fix the problem, modify scriptname to start with an interpreter line of the form

For more information, see web search results for shebang+line.