Difference between revisions of "Step-by-step debugging guide"

From ArchWiki
Jump to navigation Jump to search
m (Style: various fixes)
m (→‎Readelf: fixed a typo)
Line 107: Line 107:
If you get "no such file or directory" when running an application, try the following command:
If you get "no such file or directory" when running an application, try the following command:
  $ eadelf -a /usr/bin/appname | grep interp
  $ readelf -a /usr/bin/appname | grep interp
(replace /usr/bin/appname with the location of your executable)
(replace /usr/bin/appname with the location of your executable)

Revision as of 03:28, 9 July 2014

This page is mainly about how to gather more information in connection with bug reports. Even though the word "debug" is used, it's not intended as a guide for how to debug programs while developing.

When an application fails

Run it from the commandline

If an application suddenly crashes, try running it from a terminal emulator. Type in the name of the application in lowercase letters. If you don't know the name of the executable, only the name of the package, the following command can find the name of the executable. Replace packagename with the name of the package:

for f in `pacman -Ql packagename | grep "/bin/" | cut -d" " -f2`; do file $f 2>/dev/null | grep -q executable && basename $f; done

Check if the application segfaults

If you see the word "segfault" or the phrase "segmentation fault", see if there is a file named "core" as well.

ls core

If there is, the application has segfaulted. The "core" file can, if the application is compiled in a debug-friendly way, be used to find out where things went wrong. Sometimes the core file ends up in one of the directories the application has visited, instead of the current directory.

If you can't find the "core" file, it may be the case that core dumping is disabled by default. Use $ ulimit -c unlimited before executing the faulty program, you may also add this to .bashrc to aid in future debugging.

Segmentation faults

There are several techniques that can be used to figure out what went wrong. Put your detective hat on.


gdb is an ancient and well tested application for debugging applications. Replace appname with the name of your executable:

$ gdb appname
(wait for segfault)
bt full

Now post the output to a Pastebin client and include the URL in your bug report.

Improved gdb output

Merge-arrows-2.pngThis article or section is a candidate for merging with Debug - Getting Traces.Merge-arrows-2.png

Notes: Same subject (Discuss in Talk:Step-by-step debugging guide#)

First recompile the application in question with the -g, -O0 and -fbuiltin flags. Make sure "!strip" is in the options array in the PKGBUILD, then install the package and run it again with gdb, as above.

This is how the options line can look:


One way of enabling -g, -O0 and -fbuiltin is to put these two lines at the very beginning of the build() function in the relevant PKGBUILD:

export CFLAGS="$CFLAGS -O0 -fbuiltin -g"
export CXXFLAGS="$CXXFLAGS -O0 -fbuiltin -g"

The meaning of the flags is the following: -g enables debug symbols and -O0 turns off optimizations. (-O2 is the most common optimization level. (-O3 is usually overkill and -O4 and above behaves exactly like -O3).

If you have a "core" file, it can be used together with gdb to get a backtrace:

$ gdb appname core
bt full


Assuming you have an unstripped binary without inlined functions, it's usually a good idea to also run that program through valgrind. valgrind is a tool that emulates a CPU and usually shows where things go wrong or provide additional info in addition to gdb.

$ valgrind appname

it will provide a lot of helpful debug output if there is a crash. Consider -v and --leak-check=full to get even more info.

Alternatively, use:

$ valgrind --tool=callgrind appname

and run the output through kdesdk-kcachegrind to graphically explore the functions the program uses. If a program hangs, this makes it easier to pinpoint the location of the error.

Missing files or libraries


strace finds out in detail what an application is actually doing. If an application tries to open a file that isn't there, it can be discovered by strace.

For finding which files a program named appname tries to open:

$ strace -eopen appname

Save the output, post it to a Pastebin client and keep the URL in handy.

Tip: If you wish to grep the output from strace, you can try:

strace -o /dev/stdout appname | grep string


Setting LD_DEBUG=files gives another overview of what files an application is looking for. For an application named appname:

LD_DEBUG=files appname > appname.log 2>&1

The output will end up in appname.log.

For more information, see man ld-linux.


If you get "no such file or directory" when running an application, try the following command:

$ readelf -a /usr/bin/appname | grep interp

(replace /usr/bin/appname with the location of your executable)

Make sure the interpreter in question (like /lib/ld-linux-x86-64.so.2) actually exists. Install ld-lsbAUR from the AUR if need be.

If it's not written in C or C++, but perhaps in Python

Use file on the executable to get more information (replace "appname" with your executable):

$ file /usr/bin/appname

If it says "ELF" it's a binary exectuable and is usually written in C or C++. If it says "Python script" you know you're dealing with an application written in Python.

If it's a shell script, open up the shell script in a text editor and see (usually at the bottom of the file) if you can find the name of the real application (ELF file). You can then temporarily put "gdb" right in the shellscript, before the name of the executable, for debugging purposes. See the sections about gdb further up.

For pure shell scripts, you can also use bash -x script_name or bash -xv script_name.

For Python applications, the output will often say which file and line number the crash occured at. If you're proficient with Python, you can try to fix this and include the fix in the bug report.

Report the bug

Please report a bug at https://bugs.archlinux.org and possibly also directly to the developers of the application in question, then include a link in the Arch Linux bug report. This helps us all.

However, if you think there's something wrong with the application itself, and not with how it is packaged, report the bug directly to upstream (which means the developers of the application). Normally, software streams from developers, through packagers/maintainers and down to users. Upstream means the other way, so for this case: directly to the developers of an application.

See also