GDB-9.2
Introduction to GDB
GDB, the GNU Project debugger,
allows you to see what is going on “inside”
another program while it executes -- or what another program was
doing at the moment it crashed. Note that GDB is most effective when tracing programs
and libraries that were built with debugging symbols and not
stripped.
This package is known to build and work properly using an LFS-10.0
platform.
Package Information
GDB Dependencies
Recommended Runtime Dependency
six-1.15.0 (Python 3 module, required at run-time
to use GDB scripts from various LFS/BLFS packages with Python 3
installed in LFS)
Optional
Doxygen-1.8.19, GCC-10.2.0 (ada and gfortran are
used for tests), Guile-3.0.4, Python-2.7.18, rustc-1.42.0 (used for some
tests), Valgrind-3.16.1, and SystemTap (run-time, used
for tests)
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/gdb
Installation of GDB
Install GDB by running the
following commands:
mkdir build &&
cd build &&
../configure --prefix=/usr \
--with-system-readline \
--with-python=/usr/bin/python3 &&
make
Optionally, to build the API documentation using Doxygen-1.8.19, run:
make -C gdb/doc doxy
To test the results, issue:
pushd gdb/testsuite &&
make site.exp &&
echo "set gdb_test_timeout 120" >> site.exp &&
runtest
popd
See gdb/testsuite/README and
TestingGDB. There
are many problems with the test suite:
-
Clean directories are needed if re-running the tests. For
that reason, make a copy of the compiled source code
directory before the tests in case you need to run the tests
again.
-
Results depend on installed compilers.
-
A few tests assume that the header file <sys/sdt.h>
, part of SystemTap, is
present.
-
A test run of the test suite had 230 unexpected failures (out
of over 70000 tests).
-
On some AMD-based systems, over 200 additional tests may fail
due to a difference in the threading implementation on those
CPUs.
Now, as the root
user:
make -C gdb install
If you have built the API documentation, it is now in gdb/doc/doxy.
You can install it (as the root
user):
install -d /usr/share/doc/gdb-9.2 &&
rm -rf gdb/doc/doxy/xml &&
cp -Rv gdb/doc/doxy /usr/share/doc/gdb-9.2
Command Explanations
--with-system-readline
:
This switch forces GDB to use the
copy of Readline installed in LFS.
--with-python=/usr/bin/python3
: This
switch forces GDB to use Python 3
installed in LFS. Remove this switch if you have installed
Python-2.7.18 and want to use it instead of
Python 3.
Contents
Installed Programs:
gcore, gdb and gdbserver
Installed Library:
libinproctrace.so
Installed Directories:
/usr/{include,share}/gdb and
/usr/share/doc/gdb-9.2
Short Descriptions
gcore
|
generates a core dump of a running program.
|
gdb
|
is the GNU Debugger.
|
gdbserver
|
is a remote server for the GNU debugger (it allows
programs to be debugged from a different machine).
|
libinproctrace.so
|
contains functions for the in-process tracing agent. The
agent allows for installing fast tracepoints, listing
static tracepoint markers, probing static tracepoints
markers, and starting trace monitoring.
|
Last updated on 2020-08-16 13:56:58 -0700