How to Install and Uninstall perl-Test-LeakTrace Package on openSuSE Tumbleweed
Last updated: November 07,2024
1. Install "perl-Test-LeakTrace" package
In this section, we are going to explain the necessary steps to install perl-Test-LeakTrace on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-Test-LeakTrace
Copied
2. Uninstall "perl-Test-LeakTrace" package
Please follow the steps below to uninstall perl-Test-LeakTrace on openSuSE Tumbleweed:
$
sudo zypper remove
perl-Test-LeakTrace
Copied
3. Information about the perl-Test-LeakTrace package on openSuSE Tumbleweed
Information for package perl-Test-LeakTrace:
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Test-LeakTrace
Version : 0.17-1.17
Arch : x86_64
Vendor : openSUSE
Installed Size : 53.4 KiB
Installed : No
Status : not installed
Source package : perl-Test-LeakTrace-0.17-1.17.src
Upstream URL : https://metacpan.org/release/Test-LeakTrace
Summary : Traces memory leaks
Description :
'Test::LeakTrace' provides several functions that trace memory leaks. This
module scans arenas, the memory allocation system, so it can detect any
leaked SVs in given blocks.
*Leaked SVs* are SVs which are not released after the end of the scope they
have been created. These SVs include global variables and internal caches.
For example, if you call a method in a tracing block, perl might prepare a
cache for the method. Thus, to trace true leaks, 'no_leaks_ok()' and
'leaks_cmp_ok()' executes a block more than once.
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Test-LeakTrace
Version : 0.17-1.17
Arch : x86_64
Vendor : openSUSE
Installed Size : 53.4 KiB
Installed : No
Status : not installed
Source package : perl-Test-LeakTrace-0.17-1.17.src
Upstream URL : https://metacpan.org/release/Test-LeakTrace
Summary : Traces memory leaks
Description :
'Test::LeakTrace' provides several functions that trace memory leaks. This
module scans arenas, the memory allocation system, so it can detect any
leaked SVs in given blocks.
*Leaked SVs* are SVs which are not released after the end of the scope they
have been created. These SVs include global variables and internal caches.
For example, if you call a method in a tracing block, perl might prepare a
cache for the method. Thus, to trace true leaks, 'no_leaks_ok()' and
'leaks_cmp_ok()' executes a block more than once.