Unable to Debug Multi-Threaded Application with gdb

multithreading debugging gdb beagleboard angstrom-linux
Samuel picture Samuel · Jul 20, 2012 · Viewed 25.5k times · Source

I am debugging a multi-threaded application with gdb, but when I start the program in gdb I get the warning:

warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.

I can still debug, but I can't debug anything other than the main thread. I have read forums that suggest installing the packages libthread-db1 and glibc-dbg, but this does not correct the problem for me.

On my machine I have the 3 files /lib/libthread_db.so.1, /lib/.debug/libthread_db-1.0.so, and /lib/libthread_db-1.0.so. I tried creating symbolic links in /lib with the name libthread_db.so, one time pointing at the /lib/libthread_db.so.1 file, and another time pointing at the /lib/libthread_db-1.0.so file, and also I created the symbolic link /lib/.debug/libthread_db.so pointing to /lib/.debug/libthread_db-1.0.so, all with no luck.

In gdb I have tried setting libthread-db-search-path to /lib (with the symlink once set to libthread_db.so.1, and once to libthread_db-1.0.so, and also set to /lib/.debug.

Any suggestions? I am using Angstrom Linux v2.6.39 for the BeagleBoard-xm.

Answer

Employed Russian picture Employed Russian · Jul 21, 2012

warning: Unable to find libthread_db matching inferior's thread library

This means that your /lib/libthread_db.so.1 does not match your /lib/libpthread.so.0. Such mismatch could be the result of you installing different versions of libc and libthread_db packages, or updating one or the other outside of the package management system. It could also be an error in your packages (i.e. they may not be built correctly).

You should ignore /lib/.debug/* -- that is not the library you are looking for.

Related questions

How do I get the backtrace for all the threads in GDB?

Is there an equivalent command in GDB to that of WinDbg's "!process 0 7"? I want to extract all the threads in a dump file along with their backtraces in GDB. "info threads" doesn't output the stack traces. So, is there a …

Read More
"thread apply all bt full" gives blank in GDB

I was trying to debug a multi-threaded process on a Linux server running Slackware 12 using GDB 6.6. Once I attach and issue the command "thread apply all bt full" it comes back with nothing ( back on to the gdb prompt ). Any …

Read More
What is a thread exit code?

What exactly is a thread exit code in the Output window while debugging? What information it gives me? Is it somehow useful or just an internal stuff which should not bother me? The thread 0x552c has exited with code 259 (0…

Read More