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 |
An Extended Warning Report has all the properties and functionality of a standard warning report, but covers an extended version of the warning's core path.
The Extended Warning Report page type is available for warnings in analyzed C/C++ code only.
Important Note: the CodeSonar Web GUI makes extensive use of JavaScript. Make sure JavaScript is enabled in your web browser.
The Extended Warning Report page for a specific warning can be reached in any of the following ways.
| From Explore Callers: | [Warning and Taint+Warning mode only] Click the View Path button. |
|---|---|
| From Search Callers results: | [Warning and Taint+Warning mode only] Click listing (on the View Path line) in an expanded path entry. |
Same as standard warning report page properties.
For each warning associated with a path, CodeSonar records the execution path corresponding to the smallest call stack needed to trigger the warning. The standard Warning Report displays this path, which in general is not a full path from the program entry point. The Extended Warning Report allows users to inspect paths into the stored path fragment, adding extended path viewing functionality to the standard warning report page contents and usage.
The path displayed in the annotated code excerpt reflects a path specified by the user from a Search Callers or Explore Callers page.
In certain cases there is no extended path:
In these cases CodeSonar displays a warning above the code excerpt.
As for navigating from a standard warning report.
To report problems with this documentation, please visit https://support.codesecure.com/.