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 |
The minimum CodeSonar version for direct upgrade to CodeSonar 7.0 or later is 4.1p0. If you have a hub that is running CodeSonar 4.0p2 or earlier, contact CodeSecure support for assistance in upgrading.
If you have made changes to any of your CodeSonar configuration files, you will need to upgrade those files as part of the upgrade process.
| Release Status | For full information about release status for all current and past CodeSonar versions, see the Supported Product Versions page on the CodeSecure support site. |
|---|
| NUMBER | NAME | NOTES |
|---|---|---|
| BZ-63433 | Warning processor "resource" links no longer work | fixed |
| ZD-19124 | Parse errors when using iccarm compiler model | fixed |
| ZD-29040 | Crash in pg_dump that could interfere with hub upgrades | fixed |
| ZD-29102 | Front end crash with message "type_pointed_to: not a pointer type" when using cl compiler | fixed |
| ZD-29104 | Compatibility issue with specific HTTP reverse proxies such as Amazon Load Balancer | now actively disconnect long poll connections |
| ZD-29162 | Launchd groups not correctly created when deploying CodeSonar on Kubernetes | fixed |