How to Install and Uninstall valgrind Package on openSUSE Leap

Last updated: May 03,2024

1. Install "valgrind" package

Please follow the guidance below to install valgrind on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                valgrind
            
                    
    
    Copied

2. Uninstall "valgrind" package

Here is a brief guide to show you how to uninstall valgrind on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                valgrind
            
                    
    
    Copied

3. Information about the valgrind package on openSUSE Leap

Information for package valgrind:
---------------------------------
Repository : Main Repository
Name : valgrind
Version : 3.20.0-150500.2.1
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 28.3 MiB
Installed : No
Status : not installed
Source package : valgrind-3.20.0-150500.2.1.src
Upstream URL : https://valgrind.org/
Summary : Memory Management Debugger
Description :
Valgrind checks all memory operations in an application, like read,
write, malloc, new, free, and delete. Valgrind can find uses of
uninitialized memory, access to already freed memory, overflows,
illegal stack operations, memory leaks, and any illegal
new/malloc/free/delete commands. Another program in the package is
"cachegrind," a profiler based on the valgrind engine.
To use valgrind you should compile your application with "-g -O0"
compiler options. Afterwards you can use it with:
valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes
--db-attach=yes my_application, for example.
More valgrind options can be listed via "valgrind --help". There is
also complete documentation in the /usr/share/doc/packages/valgrind/
directory. A debugged application runs slower and needs much more
memory, but is usually still usable. Valgrind is still in development,
but it has been successfully used to optimize several KDE applications.