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.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
This task describes how to push forward an analysis that gets stuck in the "Building over; Awaiting analysis or more building" or "Building over; Native build failed" phase.
"Building over; Awaiting analysis or more building" is the expected final state if you are building a project without analyzing it, but may indicate problems if seen during an analysis or combined build/analysis.
"Building over; Native build failed" indicates that the build command being observed by CodeSonar executed with failure. This state is only possible for command-line builds: the Windows Build Wizard has no access to the exit codes of build processes and so will remain in state "Building over; Awaiting analysis or more building" if the observed build command fails.
If your problem has arisen because CodeSonar components running as services are unable to access source files that are on mapped network drives, you can resolve it by shutting down the services and then re-running CodeSonar without services.
The Windows Build Wizard has no access to the exit codes of build processes and so will remain in state "Building over; Awaiting analysis or more building" if the observed build command fails.
If you are using the Windows build wizard and have eliminated the possibility of issues with Windows services and the possibility of a build failure, "Building over; Awaiting analysis or more building" probably indicates that you have exited the build wizard or clicked Previous without clicking Finalize.
This status indicates that your underlying build command exited with failure.
Suppose that the original command line used to run the analysis was:
Then to resolve the problem:
| Fix Build System |
|
|---|---|
| Force Analysis |
|
If your system does not your system does not support IPv6 addresses, use IPv4 to specify addresses instead. For example, use 127.0.0.1:1234 instead of [::1]:1234 in the command lines in this task.