From: Nikolay Borisov <n.borisov@siteground.com>
To: systemtap@sourceware.org
Subject: printing kernel backtrace
Date: Sat, 12 Dec 2015 12:33:00 -0000 [thread overview]
Message-ID: <566C1400.1060108@siteground.com> (raw)
Hello,
I've started experimenting with systemtamp and I'd like to print the
callstack leading to the probed function. To that effect I have created
the following very simple tapset:
probe module("dm_thin_pool").function("do_waker") {
print_syms(callers(-1))
printf("finished backtrace\n");
}
However the output I get is something like that:
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffff810a5025 : 0xffffffff810a5025
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c80 : do_waker+0x0/0x40 [dm_thin_pool]
0xffffffffa0152c8 : 0xffffffffa0152c8
finished backtrace
It seems that systemtap is unable to unwind the debug information? I
believe I have compiled systemtap with the necessary unwidn libraries
but how do I check that for sure?
next reply other threads:[~2015-12-12 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 12:33 Nikolay Borisov [this message]
2015-12-12 14:38 ` Frank Ch. Eigler
2015-12-12 15:37 ` Nikolay Borisov
2015-12-12 16:01 ` Frank Ch. Eigler
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=566C1400.1060108@siteground.com \
--to=n.borisov@siteground.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).