Just a heads-up that a new version is coming soon:
Upcoming Coverity Scan upgrade to Coverity 2022.06 release
On or about August 14, 2022, a new version of Coverity Scan with improved features provided by the Coverity 2022.06 release will be available for scan.coverity.com members.
We are working to provide new releases on a more regular cadence to the open source community. Relative to the current Coverity 2021.12 release, there are significant new improvements available in this upgrade to the Coverity 2022.06 release. Some of those improvements are described in the Highlights section below.
To use Coverity 2022.06, please download the latest build tools from the download page on the scan.coverity.com site. Please refer to the instructions on the download page when they are made available.
Please note that support for Coverity 2021.12 will continue for the immediate future. Coverity 2020.09 will no longer be supported with this latest release. Please download the latest build tools after the upgrade has been completed.
The upgrade process will begin at 12 p.m. ET, and will be expected to be completed by 3 p.m. ET. The scan.coverity.com site will be unavailable when the upgrade is in process. All the features will be back online once the upgrade process is completed.
Pinned Comments
1ace commented on 2019-02-02 23:53 (UTC) (edited on 2020-01-22 10:52 (UTC) by 1ace)
To those getting a segfault: coverity has built their tool using an ancient version of glibc which they statically linked. That glibc was using a deprecated kernel API, which has been disabled (for security reasons) since kernel 4.8. They need to recompile their tool with a more recent version of glibc so that it can be used on modern Linux. They are aware of the issue (they talk about it on the front page of https://scan.coverity.com, although they got confused between sysctl and linux cmdline), but they still haven't done it 2 years later.
In the mean time, the kernel feature can be re-enabled by adding
vsyscall=emulate
to your Linux command line, although it requires the kernel to be compiled with CONFIG_X86_VSYSCALL_EMULATION=y (which is still the case of the officiallinux
package as of today). You can check that by runningzgrep CONFIG_X86_VSYSCALL_EMULATION /proc/config.gz
.