How to Install and Uninstall libdevel-gdb-perl Package on Ubuntu 16.04 LTS (Xenial Xerus)

Last updated: May 14,2024

1. Install "libdevel-gdb-perl" package

Please follow the step by step instructions below to install libdevel-gdb-perl on Ubuntu 16.04 LTS (Xenial Xerus)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                libdevel-gdb-perl
            
                    
    
    Copied

2. Uninstall "libdevel-gdb-perl" package

Learn how to uninstall libdevel-gdb-perl on Ubuntu 16.04 LTS (Xenial Xerus):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                libdevel-gdb-perl
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the libdevel-gdb-perl package on Ubuntu 16.04 LTS (Xenial Xerus)

Package: libdevel-gdb-perl
Priority: optional
Section: universe/perl
Installed-Size: 90
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Architecture: all
Version: 2.02-2
Depends: perl
Filename: pool/universe/libd/libdevel-gdb-perl/libdevel-gdb-perl_2.02-2_all.deb
Size: 24052
MD5sum: 24d2ec4fad04bc6e3913c55caf8425a6
SHA1: e95d7d6aaa49619f8f955e176f457105c4ff16db
SHA256: 91beb8cd0e57b1f23b0d3a41e217b79ad6fa8187ea499a2d267f5d5d47a7ce27
Description-en: 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: b63aeffcdcc6d2ea1c5fc607e13c7e8f
Homepage: https://metacpan.org/release/Devel-GDB
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu