From: anupam.kapoor@gmail.com (Anupam Kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Backtrace of every the threads
Date: Wed, 10 Feb 2016 14:50:16 +0530 [thread overview]
Message-ID: <87k2mcx6pb.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <CAPybu_0+Qj2CwQ0NeryDmqRZyFcA8JrSTfAOfTdfXsg5X2A-Ew@mail.gmail.com>
>>>>> [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
next prev parent reply other threads:[~2016-02-10 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 9:05 Backtrace of every the threads Ricardo Ribalda Delgado
2016-02-10 9:20 ` Anupam Kapoor [this message]
2016-02-10 9:36 ` Ricardo Ribalda Delgado
2016-02-10 10:32 ` Anupam Kapoor
2016-02-10 10:56 ` Ricardo Ribalda Delgado
2016-02-10 10:59 ` Anupam Kapoor
2016-02-10 13:37 ` Valdis.Kletnieks at vt.edu
2016-02-11 13:56 ` Ricardo Ribalda Delgado
2016-02-11 18:05 ` Valdis.Kletnieks at vt.edu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2mcx6pb.fsf@fatcat.parallelwireless \
--to=anupam.kapoor@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.