This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
user mode backtrace
- From: David Boreham <david_list at boreham dot org>
- To: SystemTap <systemtap at sources dot redhat dot com>
- Date: Thu, 19 Oct 2006 14:47:08 -0600
- Subject: user mode backtrace
- Reply-to: david_list at boreham dot org
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.