How to Install and Uninstall cppcheck Package on openSuSE Tumbleweed

Last updated: May 05,2024

1. Install "cppcheck" package

In this section, we are going to explain the necessary steps to install cppcheck on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                cppcheck
            
                    
    
    Copied

2. Uninstall "cppcheck" package

Please follow the guidance below to uninstall cppcheck on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                cppcheck
            
                    
    
    Copied

3. Information about the cppcheck package on openSuSE Tumbleweed

Information for package cppcheck:
---------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : cppcheck
Version : 2.13.3-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 9.1 MiB
Installed : No
Status : not installed
Source package : cppcheck-2.13.3-1.1.src
Upstream URL : https://github.com/danmar/cppcheck
Summary : A tool for static C/C++ code analysis
Description :
This program tries to detect bugs that your C/C++ compiler don't see. Cppcheck
is versatile. You can check non-standard code that includes various compiler
extensions, inline assembly code, etc. Checking covers for example these
errors:
* Out of bounds
* Uninitialized member variable 'classname::varname'
* Using 'memfunc' on class
* Using 'memfunc' on struct that contains a 'std::classname'
* Class Base which is inherited by class Derived does not have a virtual
destructor
* Memory leak: varname
* Resource leak: varname
* Deallocating a deallocated pointer: varname
* Using 'varname' after it is deallocated / released
* Invalid radix in call to strtol or strtoul. Must be 0 or 2-36
* Overlapping data buffer varname
* Unsigned division. The result will be wrong.
* Unusual pointer arithmetic