public inbox for
 help / color / mirror / Atom feed
From: Yibin Zhao <>
To: "Frank Ch. Eigler" <>
Subject: Re: How to translate from user space symbol name to address?
Date: Mon, 21 Nov 2022 14:44:16 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

Understood. I'm not sure if this kind of usage is common.
Finally I translated those addresses to symbols and stripped them by a post
processing script, the performance is acceptable.

On Fri, Nov 18, 2022 at 11:41 PM Frank Ch. Eigler <> wrote:

> Yibin Zhao via Systemtap <> writes:
> > I can get the ubacktrace and translate the addresses to symbols one by
> > one, and try to find the relationship between the symbol and the
> > address, but it's a bit tricky I think.
> We don't have a runtime tapset function for that direction of mapping,
> but a new one could be written, whether slowish/linear, or sorted/binary
> like the address-to-symbol table.
> - FChE

      reply	other threads:[~2022-11-21  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  9:58 Yibin Zhao
2022-11-18 15:41 ` Frank Ch. Eigler
2022-11-21  6:44   ` Yibin Zhao [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).