1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
Source: libdevel-gdb-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>,
Daniel Lintott <daniel@serverb.co.uk>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper (>= 9)
Build-Depends-Indep: gdb,
libtest-pod-coverage-perl,
libtest-pod-perl,
perl
Standards-Version: 3.9.8
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libdevel-gdb-perl.git
Vcs-Git: https://anonscm.debian.org/git/pkg-perl/packages/libdevel-gdb-perl.git
Homepage: https://metacpan.org/release/Devel-GDB
Package: libdevel-gdb-perl
Architecture: all
Depends: ${misc:Depends},
${perl:Depends}
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.
|
