From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/26670] In "end" probe, symbol lookup for user stacks is broken (print_usyms/print_ustack functions)
Date: Sun, 27 Sep 2020 19:55:12 +0000 [thread overview]
Message-ID: <bug-26670-6586-B75qNh7Cc4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26670-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26670
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
The problem is that in the end probe systemtap doesn't know with which user
space process the ustack backtrace addresses belong to (the process might even
no longer exist).
If you want to save the actual stack/symbols and use/print them in an end probe
you might want to use sprint_ustack or sprint_usyms.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-09-27 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 18:48 [Bug translator/26670] New: " barrdetwix at gmail dot com
2020-09-27 19:55 ` mark at klomp dot org [this message]
2020-09-27 21:44 ` [Bug translator/26670] " barrdetwix at gmail dot com
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-26670-6586-B75qNh7Cc4@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).