How to Install and Uninstall splint Package on Ubuntu 20.10 (Groovy Gorilla)
Last updated: November 05,2024
1. Install "splint" package
This guide covers the steps necessary to install splint on Ubuntu 20.10 (Groovy Gorilla)
$
sudo apt update
Copied
$
sudo apt install
splint
Copied
2. Uninstall "splint" package
Here is a brief guide to show you how to uninstall splint on Ubuntu 20.10 (Groovy Gorilla):
$
sudo apt remove
splint
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the splint package on Ubuntu 20.10 (Groovy Gorilla)
Package: splint
Architecture: amd64
Version: 1:3.1.2+dfsg-1build1
Multi-Arch: foreign
Priority: optional
Section: universe/devel
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian QA Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 2243
Depends: splint-data (= 1:3.1.2+dfsg-1build1), libc6 (>= 2.14)
Suggests: splint-doc-html
Breaks: splint-data (<< 1:3.1.2+dfsg-1)
Replaces: splint-data (<< 1:3.1.2+dfsg-1)
Filename: pool/universe/s/splint/splint_3.1.2+dfsg-1build1_amd64.deb
Size: 682624
MD5sum: adc5b0304cfadbce4aa935e54e30b87a
SHA1: f460901f910efb3ddca2d0868307c2f2a0e4e12a
SHA256: 1a1f8b50cdb08b55f5bea254dba97b06fae0aeb66dd26ff28e04e875363b7dea
SHA512: e2744c876e271e6afdb73f9a883b63c5c30f5d4aad42ab112f794b9e94a561af2f11185826f4f84d6cbffc573a5b3a19f8d9a21fc3006bc4421c50e82fc564aa
Homepage: http://www.splint.org/
Description-en: tool for statically checking C programs for bugs
splint is an annotation-assisted lightweight static checker. It is a tool for
statically checking C programs for security vulnerabilities and coding
mistakes. If additional effort is invested in adding annotations to programs,
splint can perform stronger checking.
.
splint does many of the traditional lint checks including unused declarations,
type inconsistencies, use before definition, unreachable code, ignored return
values, execution paths with no return, likely infinite loops, and fall
through cases. Problems detected by Splint include:
.
* Dereferencing a possibly null pointer
* Using or returning storage that is undefined or not properly defined
* Type mismatches, with greater precision and flexibility than by C compilers
* Memory management errors like use of dangling references and memory leaks
* Inconsistent (with specified interface) global variable modification or use
* Problematic control flow such as likely infinite loops etc.
* Buffer overflow vulnerabilities
* Dangerous macro implementations or invocations
* Violations of customized naming conventions
Description-md5: 8e7e32bbdb6feca91226586802c3b837
Architecture: amd64
Version: 1:3.1.2+dfsg-1build1
Multi-Arch: foreign
Priority: optional
Section: universe/devel
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian QA Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 2243
Depends: splint-data (= 1:3.1.2+dfsg-1build1), libc6 (>= 2.14)
Suggests: splint-doc-html
Breaks: splint-data (<< 1:3.1.2+dfsg-1)
Replaces: splint-data (<< 1:3.1.2+dfsg-1)
Filename: pool/universe/s/splint/splint_3.1.2+dfsg-1build1_amd64.deb
Size: 682624
MD5sum: adc5b0304cfadbce4aa935e54e30b87a
SHA1: f460901f910efb3ddca2d0868307c2f2a0e4e12a
SHA256: 1a1f8b50cdb08b55f5bea254dba97b06fae0aeb66dd26ff28e04e875363b7dea
SHA512: e2744c876e271e6afdb73f9a883b63c5c30f5d4aad42ab112f794b9e94a561af2f11185826f4f84d6cbffc573a5b3a19f8d9a21fc3006bc4421c50e82fc564aa
Homepage: http://www.splint.org/
Description-en: tool for statically checking C programs for bugs
splint is an annotation-assisted lightweight static checker. It is a tool for
statically checking C programs for security vulnerabilities and coding
mistakes. If additional effort is invested in adding annotations to programs,
splint can perform stronger checking.
.
splint does many of the traditional lint checks including unused declarations,
type inconsistencies, use before definition, unreachable code, ignored return
values, execution paths with no return, likely infinite loops, and fall
through cases. Problems detected by Splint include:
.
* Dereferencing a possibly null pointer
* Using or returning storage that is undefined or not properly defined
* Type mismatches, with greater precision and flexibility than by C compilers
* Memory management errors like use of dangling references and memory leaks
* Inconsistent (with specified interface) global variable modification or use
* Problematic control flow such as likely infinite loops etc.
* Buffer overflow vulnerabilities
* Dangerous macro implementations or invocations
* Violations of customized naming conventions
Description-md5: 8e7e32bbdb6feca91226586802c3b837