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

multithreading debugging gdb backtrace
srikantha ks picture srikantha ks · Aug 23, 2013 · Viewed 138.1k times · Source

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 command that does?

Answer

Sharad picture Sharad · Apr 10, 2014

Generally, the backtrace is used to get the stack of the current thread, but if there is a necessity to get the stack trace of all the threads, use the following command.

thread apply all bt

Related questions

Unable to Debug Multi-Threaded Application with gdb

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, …

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