From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/25853] Stap's own dwarf-based stack unwinder does not give very accurate kernel backtraces
Date: Mon, 28 Sep 2020 21:22:38 +0000 [thread overview]
Message-ID: <bug-25853-6586-faoChgzkfX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25853-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25853
--- Comment #1 from agentzh <agentzh at gmail dot com> ---
Adding the '-d kernel' option is not very helpful when the kernel debuginfo is
missing in the system:
```
$ /opt/stap/bin/stap -d kernel -e 'probe oneshot { print_backtrace() }'
0xffffffffc123c8cb [stap_e4014a9c5a0decc7f01b4bb37a893a9_29973+0x88cb/0x0]
0xffffffffc123c84a [stap_e4014a9c5a0decc7f01b4bb37a893a9_29973+0x884a/0x0]
(inexact)
```
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2020-09-28 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 19:51 [Bug runtime/25853] New: " agentzh at gmail dot com
2020-09-28 21:22 ` agentzh at gmail dot com [this message]
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=bug-25853-6586-faoChgzkfX@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).