GUI: Logs: Analysis Log

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.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

CodeSonar^® 9.2p0

CONFIDENTIAL

CodeSecure Inc

General

GUI Reference: Logs: Analysis Log

The analysis phase occurs after all software components have been built into the CodeSonar project. During this phase, CodeSonar links the different files together and analyzes the whole program. Warnings are issued during this phase.

The Analysis Log is available for all analyses, independent of the language or languages involved.

Navigating To
Page Properties
Contents and Usage
Navigating From
Related Tasks

Note: The log will be updated with analysis daemon output until the daemon exits. The analysis log buffer is flushed every 60 seconds, so output may take up to a minute to appear on the Analysis Log page.

To shut down all daemons currently associated with the hub and flush any outstanding analysis log content, use the close_all hub command.
To shorten the timeout period for daemons started by future analyses, set configuration file variable DAEMON_TIMEOUT to a lower (positive) value.

Navigating To

From any log page:

Click show logs (on the Finished line) to expand the list of logs, then click one of the links on the codesonar analysis line. If the logs for the analysis have been deleted, the show logs link will not be active.

From Analysis:

Expand the Analysis Details section, then click one of the links on the Logs codesonar analysis line. If the logs for the analysis have been deleted, the Logs section will contain a "logs have been deleted" notification instead of a table of links.

If the analysis state is anywhere between Linking to Analyzing (inclusive), or is Stalled, you can also click on the Analysis State progress bar to navigate to the Analysis Log.
If the analysis is Stalled, there will also be An "Analysis Stalled " Alert that links to the Analysis Log.

From Source Listing:

Expand the File Details section, click show logs (on the Finished line) to expand the list of logs, then click one of the links on the codesonar analysis line. If the logs for the analysis have been deleted, the show logs link will not be active.

by URL:

The URL depends on the log view required:

Full	http://hub_location/analysis/analysis_id-ad_log.html
Streamed Full	http://hub_location/analysis/analysis_id-ad_logstream.html
Tail	http://hub_location/analysis/analysis_id-ad_logtailnum.html
Streamed Tail	http://hub_location/analysis/analysis_id-ad_logstreamtailnum.html

Where num in the Tail and Streamed Tail URLs specifies the number of rows to retrieve from the log database for display (or initial display, if the log is streamed).

Page Properties

Output formats

XML (log_basic.xsd), text

Visibility Filter Applied

none

RBAC Permissions Needed

Page Access	ANALYSIS_READ ANALYSIS_WARNING_EXISTS

Contents and Usage

The following annotated screenshot shows the various parts of an Analysis Log page.

Annotated Screenshot: Analysis Page

Standard Header

See GUI Reference: Standard Header.

Breadcrumbs

Home > [Other_ProjectTree_Ancestors >] Project_Name > Analysis_Name > CodeSonar Analysis Log
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 project analyzed by this analysis, 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.

Page Heading

Project_Name : Analysis_Name : CodeSonar Analysis Log

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.
Finished	click show logs for links to the analysis Build Log, CodeSonar Parse Log, and CodeSonar Analysis Log. 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

Zero or more lines of text, representing a transcription of the interleaved stdout and stderr messages issued by the CodeSonar analysis phase.

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 parse log, or see a different view of the analysis log	Click show logs, then select the desired log and view from the list of links.

Related Tasks

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