From mboxrd@z Thu Jan  1 00:00:00 1970
From: anupam.kapoor@gmail.com (Anupam Kapoor)
Date: Wed, 10 Feb 2016 14:50:16 +0530
Subject: Backtrace of every the threads
In-Reply-To: <CAPybu_0+Qj2CwQ0NeryDmqRZyFcA8JrSTfAOfTdfXsg5X2A-Ew@mail.gmail.com>
References: <CAPybu_0+Qj2CwQ0NeryDmqRZyFcA8JrSTfAOfTdfXsg5X2A-Ew@mail.gmail.com>
Message-ID: <87k2mcx6pb.fsf@fatcat.parallelwireless>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org


>>>>> [2016-02-10T14:35:33+0530]: "Ricardo Ribalda Delgado" (ricardo-delgado):

,----[ ricardo-delgado ]
| Luckily, the error is gone now :). but I was wondering if there is a
| way to show the backtrace of ALL the threads in the system, which
| could have been a wonderful tool to debug this issue.
`----
from the gdb info page:

In a multi-threaded program, gdb by default shows the backtrace only for
the current thread. To display the backtrace for several or all of the
threads, use the command thread apply (see thread apply). For example,
if you type thread apply all backtrace, gdb will display the backtrace
for all the threads; this is handy when you debug a core dump of a
multi-threaded program.

hope that's what you are looking for ?

--

kind regards
anupam