Debian Codegraph @

debian/control

raw
1 Source: libdevel-gdb-perl
2 Maintainer: Debian Perl Group <[email protected]>
3 Uploaders: gregor herrmann <[email protected]>
4 Section: perl
5 Testsuite: autopkgtest-pkg-perl
6 Priority: optional
7 Build-Depends: debhelper-compat (= 13)
8 Build-Depends-Indep: gdb,
9 libtest-pod-coverage-perl,
10 libtest-pod-perl,
11 perl
12 Standards-Version: 3.9.8
13 Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdevel-gdb-perl
14 Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdevel-gdb-perl.git
15 Homepage: https://metacpan.org/release/Devel-GDB
16
17 Package: libdevel-gdb-perl
18 Architecture: all
19 Depends: ${misc:Depends},
20 ${perl:Depends}
21 Multi-Arch: foreign
22 Description: module to open and communicate with a gdb session
23 The Devel::GDB package provides an interface for communicating
24 with GDB. Internally, it uses the GDB/MI interpreter
25 (see http://sourceware.org/gdb/current/onlinedocs/gdb_25.html),
26 which accurately informs the caller of the program state and,
27 through the use of tokens, guarantees that the results returned
28 actually correspond to the request sent.
29 By contrast, GDB's console interpreter returns all responses on
30 STDOUT, and thus there is no way to ensure that a particular response
31 corresponds to a particular request.
32 .
33 Therefore, it is obviously preferable to use GDB/MI when programmatically
34 interacting with GDB. This can be done via the send_cmd family of functions
35 (send_cmd, send_cmd_excl, and send_cmd_async). There are, however,
36 some cases when there is no GDB/MI command corresponding to a particular
37 console command, or it has not yet been implemented (for example, -symbol-type,
38 corresponding to the console command ptype, is not yet implemented as of GDB
39 6.6). In this case, the get function provides a workaround by capturing all
40 output sent to the console stream.