How to Install and Uninstall libdevel-gdb-perl Package on Kali Linux
Last updated: February 03,2025
1. Install "libdevel-gdb-perl" package
Please follow the steps below to install libdevel-gdb-perl on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
libdevel-gdb-perl
Copied
2. Uninstall "libdevel-gdb-perl" package
Please follow the steps below to uninstall libdevel-gdb-perl on Kali Linux:
$
sudo apt remove
libdevel-gdb-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libdevel-gdb-perl package on Kali Linux
Package: libdevel-gdb-perl
Version: 2.02-6
Installed-Size: 59
Maintainer: Debian Perl Group
Architecture: all
Depends: perl:any
Size: 22888
SHA256: 1026028942fb372b33fd7e276a8fea7bf7b287ff43e5892ba83500af09b501ed
SHA1: 8e17e19d56b99da9fc78e1787ff6f484e0588c07
MD5sum: de15e411d6629c60e85373513ad1032a
Description: module to open and communicate with a gdb session
The Devel::GDB package provides an interface for communicating
with GDB. Internally, it uses the GDB/MI interpreter
(see http://sourceware.org/gdb/current/onlinedocs/gdb_25.html),
which accurately informs the caller of the program state and,
through the use of tokens, guarantees that the results returned
actually correspond to the request sent.
By contrast, GDB's console interpreter returns all responses on
STDOUT, and thus there is no way to ensure that a particular response
corresponds to a particular request.
.
Therefore, it is obviously preferable to use GDB/MI when programmatically
interacting with GDB. This can be done via the send_cmd family of functions
(send_cmd, send_cmd_excl, and send_cmd_async). There are, however,
some cases when there is no GDB/MI command corresponding to a particular
console command, or it has not yet been implemented (for example, -symbol-type,
corresponding to the console command ptype, is not yet implemented as of GDB
6.6). In this case, the get function provides a workaround by capturing all
output sent to the console stream.
Description-md5:
Multi-Arch: foreign
Homepage: https://metacpan.org/release/Devel-GDB
Tag: devel::lang:perl, devel::library, implemented-in::perl, role::shared-lib
Section: perl
Priority: optional
Filename: pool/main/libd/libdevel-gdb-perl/libdevel-gdb-perl_2.02-6_all.deb
Version: 2.02-6
Installed-Size: 59
Maintainer: Debian Perl Group
Architecture: all
Depends: perl:any
Size: 22888
SHA256: 1026028942fb372b33fd7e276a8fea7bf7b287ff43e5892ba83500af09b501ed
SHA1: 8e17e19d56b99da9fc78e1787ff6f484e0588c07
MD5sum: de15e411d6629c60e85373513ad1032a
Description: module to open and communicate with a gdb session
The Devel::GDB package provides an interface for communicating
with GDB. Internally, it uses the GDB/MI interpreter
(see http://sourceware.org/gdb/current/onlinedocs/gdb_25.html),
which accurately informs the caller of the program state and,
through the use of tokens, guarantees that the results returned
actually correspond to the request sent.
By contrast, GDB's console interpreter returns all responses on
STDOUT, and thus there is no way to ensure that a particular response
corresponds to a particular request.
.
Therefore, it is obviously preferable to use GDB/MI when programmatically
interacting with GDB. This can be done via the send_cmd family of functions
(send_cmd, send_cmd_excl, and send_cmd_async). There are, however,
some cases when there is no GDB/MI command corresponding to a particular
console command, or it has not yet been implemented (for example, -symbol-type,
corresponding to the console command ptype, is not yet implemented as of GDB
6.6). In this case, the get function provides a workaround by capturing all
output sent to the console stream.
Description-md5:
Multi-Arch: foreign
Homepage: https://metacpan.org/release/Devel-GDB
Tag: devel::lang:perl, devel::library, implemented-in::perl, role::shared-lib
Section: perl
Priority: optional
Filename: pool/main/libd/libdevel-gdb-perl/libdevel-gdb-perl_2.02-6_all.deb