%general-entities; ]> $LastChangedBy$ $Date$ 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. &lfs79_checked; Package Information Download (HTTP): Download (FTP): Download MD5 sum: &gdb-md5sum; Download size: &gdb-size; Estimated disk space required: &gdb-buildsize; Estimated build time: &gdb-time; GDB Dependencies Optional (for tests), , , , , and SystemTap (run-time dependency, also used in a few tests) User Notes: Install GDB by running the following commands: ./configure --prefix=/usr --with-system-readline && make Optionally, to build the API documentation using , 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 TRANSCRIPT=y popd See gdb/testsuite/README and TestingGDB. There are many problems with the test suite. First one is that you need to clean some directories, if re-running the tests. For that reason, it is recommended to 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, 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. A few tests assume that the header file <sys/sdt.h>, part of SystemTap, is present. Unexpected failures are less than 0.3%. 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-&gdb-version; && rm -rf gdb/doc/doxy/xml && cp -Rv gdb/doc/doxy /usr/share/doc/gdb-&gdb-version; Installed Programs Installed Library Installed Directories gcore, gdb and gdbserver libinproctrace.so /usr/{include,share}/gdb and /usr/share/doc/gdb-&gdb-version; Short Descriptions gcore generates a core dump of a running program. gcore gdb is the GNU Debugger. gdb-prog gdbserver is a remote server for the GNU debugger (it allows programs to be debugged from a different machine). gdbserver 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. libinproctrace.so