From: ricardo.ribalda@gmail.com (Ricardo Ribalda Delgado)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Backtrace of every the threads
Date: Wed, 10 Feb 2016 10:05:33 +0100 [thread overview]
Message-ID: <CAPybu_0+Qj2CwQ0NeryDmqRZyFcA8JrSTfAOfTdfXsg5X2A-Ew@mail.gmail.com> (raw)
Hello
I have been debugging a process that makes a syscall which never
returned. The problem was the interaction between than process and
other kernel threads, due to an error on the way the locks were
designed (my bad).
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.
Things that I tried and NOT worked:
1) perf top:
It is fast and easy if the tasks are in active loops, but if they are
sleeping, waiting for an event, holding a lock.... they will not
appear.
2) ftrace
works, but there are MILLIONS of lines to navigate :S Unless there is
a good way to navigate the data it is a "last resource" tool.
3) gdb vmlinux /proc/kcore; info threads
I had big hopes on this... but only one thread was showed.
Are the Linux awareness gdb extensions ready?
4) sysrq, print backtrace
It only shows the active threads, not the "waiting" ones
What I want?
A magic command that shows the backtrace of ALL the threads (kernel
and userland). Something like a ps with steroids.
Does this exist? Where would be the best place to start developing
something like this: perf people, unix-utils, systemd :S , alone in a
dark basement?
Thanks!
--
Ricardo Ribalda
next reply other threads:[~2016-02-10 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 9:05 Ricardo Ribalda Delgado [this message]
2016-02-10 9:20 ` Backtrace of every the threads Anupam Kapoor
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=CAPybu_0+Qj2CwQ0NeryDmqRZyFcA8JrSTfAOfTdfXsg5X2A-Ew@mail.gmail.com \
--to=ricardo.ribalda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).