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-7.7
This package is known to build and work properly using the gcc-5
DejaGnu-1.5.3 (for tests), Doxygen-184.108.40.206,
Guile-2.0.11, and Python-2.7.10
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/gdb
Installation of GDB
Install GDB by running the
./configure --prefix=/usr --with-system-readline &&
Optionally, to build the API documentation using Doxygen-220.127.116.11,
make -C gdb/doc doxy
To test the results, issue: make -k
check. There are many problems with the test suite.
Depends on installed compilers, there are differences if run
locally or remotely, a large number of timeouts (there is a
variable that can be set to increase time for timeout, but changing
it, apparently the total number of tests is not conserved), there
are failures associated with system readline 6.x, between others.
Unexpected failures are of the order of 0.5%.
Now, as the
make -C gdb install
If you have built the API documentation, it is now in gdb/doc/doxy.
You can install it (as the
install -d /usr/share/doc/gdb-7.9.1 &&
cp -Rv gdb/doc/doxy /usr/share/doc/gdb-7.9.1