From: David Boreham <david_list@boreham.org>
To: SystemTap <systemtap@sources.redhat.com>
Subject: user mode backtrace
Date: Thu, 19 Oct 2006 20:47:00 -0000 [thread overview]
Message-ID: <4537E44C.6040604@boreham.org> (raw)
I'd like to get a stack trace for the process that made the
system call I'm probing (I'm looking at filesystem access
typically, so reads/writes/syncs etc). The systemtap backtrace
function appears to only get the kernel mode stack which
is not much use to me. I was wondering if anyone had
discovered a good solution to this problem already ?
I was thinking perhaps I could invoke pstack (gdb)
on the current pid/tid. But I'm worried that doing so
might deadlock since the process is inside a system
call.
I'm looking at a very large application that beats up on
the filesystem, in case you're wondering why I want to do
this. It's so large that nobody is quite sure what code
access which files, when and why.
Thanks.
next reply other threads:[~2006-10-19 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 20:47 David Boreham [this message]
2006-10-19 22:33 ` Vara Prasad
2006-10-19 22:51 ` David Boreham
2006-10-20 14:28 ` William Cohen
2006-10-20 14:50 ` David Boreham
2006-10-19 23:50 ` Frank Ch. Eigler
2006-10-20 0:15 ` David Boreham
2006-10-20 0:27 ` Frank Ch. Eigler
2006-10-19 22:56 Stone, Joshua I
2006-10-19 23:07 ` David Boreham
2006-10-19 23:24 ` David Boreham
2006-10-20 0:09 ` Frank Ch. Eigler
2006-10-20 2:02 Stone, Joshua I
2006-10-20 2:13 Stone, Joshua I
2006-10-20 18:34 Stone, Joshua I
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=4537E44C.6040604@boreham.org \
--to=david_list@boreham.org \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).