Debug - Getting Traces
This article aims to help in creating a debugging Arch package and using it to provide trace and debug information for reporting software bugs to developers.
- 1 Discovering name of package(s)
- 2 Obtaining PKGBUILD
- 3 Compilation settings
- 4 Building and installing the package
- 5 Getting the trace
- 6 Conclusion
- 7 See also
Discovering name of package(s)
A few facts of debug messages
When looking at debug message, such as:
[...] Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1241265952 (LWP 12630)] (no debugging symbols found) 0xb7f25410 in __kernel_vsyscall () #0 0xb7f25410 in __kernel_vsyscall () #1 0xb741b45b in ?? () from /lib/libpthread.so.0 [...]
you can see
?? at the place where debugging info is missing and also the name of library or executable which called the function. Similarly, when the line
(no debugging symbols found) appears in a message, it means that you have to look for a file whose name is stated.
Use Pacman to retrieve name of package:
# pacman -Qo /lib/libthread_db.so.1 /lib/libthread_db.so.1 is owned by glibc 2.5-8
We have found that package is calledin version 2.5-8. By repeating this step, we are able to create a list of packages which we have to compile ourselves to get full stack trace.
In order to build a package from source, the PKGBUILD file is required. The location from which you can obtain PKGBUILDs is, in general:
Use AUR search page to find the package. If it is not present, the package is stored in one of the official repository trees of Arch Linux. If found, click on its name and download the
tar to extract it and change the directory:
$ tar xvzf name_of_tarball.tar.gz $ cd name_of_tarball
If the package is a part of official tree, install ABS, fetch the source for the package and then build it:
$ ABSROOT=. abs core/glibc $ cd core/glibc $ makepkg -s
At this stage, you can modify the global configuration file of
makepkg if you will be using it only for debug purposes. In other cases, you should modify package's PKGBUILD file only for each package you would like to rebuild.
makepkg's configuration file
/etc/makepkg.conf to contain following lines:
CFLAGS="-g -march=i686 -O1 -pipe" CXXFLAGS="-g -march=i686 -O1 -pipe"
(change i686 with x86-64 if using 64-bit system)
OPTIONS=(!strip !docs libtool emptydirs)
These settings (in bold) will force compilation with debugging information and will disable the stripping of executables.
One package settings only
foo's PKGBUILD file to contain the following lines:
build() function, add following lines at the very beginning:
export CFLAGS="$CFLAGS -g -O1" export CXXFLAGS="$CXXFLAGS -g -O1"
In addition to the previous general settings you should pass
-developer-build option to the
configure script in the
PKGBUILD. Also compiling Qt with qtwebkit installed may cause compilation errors. That is why you would also want to remove qtwebkit package temporarily from your system. Use the following command in order to ignore any dependencies on qtwebkit.
# pacman -Rdd qtwebkit
Do not forget to install qtwebkit after the compilation of Qt is finished, otherwise the programs that depend on it will not work!
KDE and software built with KDE technologies normally use CMake for build. To build this software with debug symbols change the option
Building and installing the package
Build the package from source using
makepkg while in the PKGBUILD's directory. This could take some time:
Then install the built package:
# pacman -U glibc-2.5-8-i686.pkg.tar.gz
Getting the trace
The actual backtrace (or stack trace) can now be obtained via e.g., the GNU Debugger. Run it either via:
# gdb /path/to/file
# gdb (gdb) exec /path/to/file
The path is optional, if already set in the
run followed by any arguments you wish the program to start with, e.g.:
(gdb) run --no-daemon --verbose
to start execution of the file. Do whatever necessary to evoke the bug. For the actual log, type the lines:
(gdb) set logging file trace.log (gdb) set logging on
to output the trace to
trace.log into the directory
gdb was started in. To exit, enter:
(gdb) set logging off (gdb) quit
Use the complete stack trace to inform developers of a bug you have discovered before. This will be highly appreciated by them and will help to improve your favorite program.