JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

CodeSonar® 9.2p0 CONFIDENTIAL CodeSecure Inc
General

GUI Reference: Logs: Native Compilation Details Log

A Native Compilation Details Log page contains detailed information about CodeSonar's treatment of a single compiler invocation from within the hooked build command.

Native compilation details logs are only available when configuration parameter SEND_HOOK_LOG_TO_HUB is set to Yes.

Navigating To

From Parse Log In the log entry for the compiler invocation of interest, click the compiler command in the entry header.

Native compilation details logs are only sent to the hub when configuration parameter SEND_HOOK_LOG_TO_HUB is set to Yes. If it is set to No for a particular analysis, Native Compilation Details Log pages will not be available for that analysis and the Parse Log page will not contain any logging information.

Page Properties

Output formats XML (log_spawncs_details.xsd), text
Visibility Filter Applied none
RBAC Permissions Needed
Page AccessANALYSIS_READ

Contents and Usage

The following annotated screenshot shows the various parts of a Native Compilation Details Log page.

Annotated Screenshot: Native Compilation Details Log Page standard header breadcrumbs basic analysis information the build log standard footer

Standard Header See GUI Reference: Standard Header.
Breadcrumbs Home > [Other_ProjectTree_Ancestors >] Project_Name > Analysis_Name > Parse Log > Command_Line
where
  • Home links to the GUI Home page.
  • Together with the Home link (corresponding to the root project tree), Other_ProjectTree_Ancestors represents the project tree ancestors of the analyzed project as a >-separated sequence of project tree names. Each name links to the corresponding Project Tree page.
  • Project_Name is the name of the analyzed project, and links to the corresponding Project page.
  • Analysis_Name is the value of the Analysis property for this analysis, and links to the corresponding Analysis page.
  • Parse Log links to the Parse Log page for this analysis.
  • Command_Line is the hooked command line (issued by the user's build system) that is detailed on this page.
Page Heading The Native Compilation Details Log page has no heading.
Basic Analysis Information A table of basic information about the analysis:
Project Description (if any) for the project analyzed.
Analysis  
Analysis Description (if any)
Started click show details to view the analysis Username, Machine, and Address.

screenshot fragment: show details expansion

Finished click show logs for links to the analysis Build Log, CodeSonar Parse Log, and CodeSonar Analysis Log.

screenshot fragment: show logs expansion

If logs for this analysis have been deleted, a "logs have been deleted" notification will be displayed instead of the table of links. (Logs can be deleted from the Analysis page.)
Analysis State A progress bar if the CodeSonar analysis is still running; "Analysis finished" if the analysis has completed.
Log Details A table of information about the compiler invocation:
Command Started The time at which the command was invoked during the hooked build.
Command Status The current status of the command.
Command Line The full hooked command line.
CodeSonar Command Line The CodeSonar command that was generated to analyze Command Line.
CodeSecure Diagnostic output If the VERBOSITY setting is 6 or higher, the log will include messages produced by CodeSonar during execution of the CodeSonar Command Line. There are several different message types, including the following.
  • patch applied: patchdirpath/sourcefname/patchfname
    The source file patch in patchdirpath/sourcefname/patchfname has been applied to file sourcefname.
  • patch discarded: patchdirpath/sourcefname/patchfname
    The source file patch in patchdirpath/sourcefname/patchfname was not applied to file sourcefname because one or more of its hunks could not be applied.
  • patched version of sourcepath/sourcefname cached as cachepath/cachefname
    All applicable source file patches have been applied to sourcefname, and a copy of the patched file has been cached at the specified location.
  • reusing patched version of sourcepath/sourcefname from cachepath/cachefname
    CodeSonar identified a cached, patched version of sourcefname.
  • no patch applied for sourcepath/sourcefname, save original as cachepath/cachefname
    At least one source patch subdirectory for sourcefname was identified, but there were no applicable patches. An unmodified copy of sourcefname has been cached at the specified location. (In contrast, if there was no source patch subdirectory for sourcefname, CodeSonar would not issue any patch messages for sourcefname at all.)
  • new replacement cachepath/rep_fname for path/to/fname
    All source replacement commands — as specified by SOURCE_PATTERN_REPLACEMENT and SOURCE_REPLACE_COMMAND rules — have been carried out on file fname, with the resulting file cached at the specified location. For source files with no applicable patches, path/to/fname will refer to the underlying source file, otherwise it will refer to the cached version of the patched file as reported by the corresponding patched version... or reusing patched version... message.
  • reusing replacement cachepath/rep_fname for path/to/fname
    CodeSonar has identified a previously cached version of a source file. As for new replacement... messages, path/to/fname will refer to either the underlying source file or the cached version of the patched file, depending on whether any patches were applicable.
  • Patch failed because the patch file patchdirpath/sourcefname/patchfname is malformed [...]
    CodeSonar's source file patching module identified a problem in patch file patchdirpath/sourcefname/patchfname that renders it inapplicable to any source file. The "Patch failed" notification is followed by a brief description of the problem encountered in the specified file. If this description is not sufficient, set environment variable GT_DEBUG_SOURCE_PATCH to 1 and run the CodeSonar build again to obtain additional trace output.
errors Any parse errors will be listed after the CodeSonar command line.
Compilation Units Compiled For each compilation unit generated by this compiler invocation, the full path to the file instance at the root of the compilation unit. Each path links to the Parse Details Log page for that compilation unit.

If logs for this analysis have been deleted, a deletion notification will be displayed instead.
Standard Footer See GUI Reference: Standard Footer.

Navigating From

view the analysis build or analysis log or see a different view of the parse log Click show logs, then select the desired log and view from the list of links.
view the parse details log corresponding to a compilation unit compiled by this command Click the link in the Compilation Units Compiled: section of the log details.
 

To report problems with this documentation, please visit https://support.codesecure.com/.