How to Install and Uninstall ltrace Package on openSUSE Leap
Last updated: December 23,2024
1. Install "ltrace" package
Please follow the instructions below to install ltrace on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
ltrace
Copied
2. Uninstall "ltrace" package
Learn how to uninstall ltrace on openSUSE Leap:
$
sudo zypper remove
ltrace
Copied
3. Information about the ltrace package on openSUSE Leap
Information for package ltrace:
-------------------------------
Repository : Main Repository
Name : ltrace
Version : 0.7.91-150500.18.1
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 411.1 KiB
Installed : No
Status : not installed
Source package : ltrace-0.7.91-150500.18.1.src
Upstream URL : https://ltrace.org/
Summary : Library and system call tracer for programs
Description :
Ltrace is a program that runs the specified command until it exits. It
intercepts and records the dynamic library calls that are called by the
executed process and the signals that are received by that process. It
can also intercept and print the system calls executed by the program.
The program to trace need not be recompiled for this, so ltrace can be
used on binaries for which no source is available.
This is still a work in progress, so, for example, the tracking to
child processes may fail or some things may not work as expected.
-------------------------------
Repository : Main Repository
Name : ltrace
Version : 0.7.91-150500.18.1
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 411.1 KiB
Installed : No
Status : not installed
Source package : ltrace-0.7.91-150500.18.1.src
Upstream URL : https://ltrace.org/
Summary : Library and system call tracer for programs
Description :
Ltrace is a program that runs the specified command until it exits. It
intercepts and records the dynamic library calls that are called by the
executed process and the signals that are received by that process. It
can also intercept and print the system calls executed by the program.
The program to trace need not be recompiled for this, so ltrace can be
used on binaries for which no source is available.
This is still a work in progress, so, for example, the tracking to
child processes may fail or some things may not work as expected.