linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Tony Jones <tonyj@suse.de>
Cc: linux-perf-users@vger.kernel.org, irogers@google.com
Subject: Re: addr2line performance
Date: Mon, 3 Nov 2025 19:16:11 -0800	[thread overview]
Message-ID: <aQlv-w0axiiMrZVD@google.com> (raw)
In-Reply-To: <aQUe14AOt3Yc5Xv0@suse.de>

Hello,

On Fri, Oct 31, 2025 at 01:40:55PM -0700, Tony Jones wrote:
> On Fri, Oct 31, 2025 at 12:39:48PM -0700, Namhyung Kim wrote:
> 
> > I think we can just use libdw.  I tried it in the past but never
> > finished. :(
> 
> This would be interesting.  
> 
> I asked our toolchain folks if they were aware of libraries 
> (other than libllvm and libbfd) that could replace the addr2line+pipe 
> (and were license compatible) but I've not heard back from them yet.
> 
> I'm happy to look into implementing this if you lack the time. LMK.

Sure, it'd be great if you can work on it.  I think it's basically
dwarf_lineaddr() followed by dwarf_linesrc() and dwarf_lineno() but
you also need to check inlined functions.

And probably you want to cache dbginfo of recent binaries to speed up
addr2line processing for the same DSOs.

Thanks,
Namhyung


      reply	other threads:[~2025-11-04  3:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 18:30 addr2line performance Tony Jones
2025-10-29 15:51 ` Ian Rogers
2025-10-31 17:01   ` Tony Jones
2025-10-31 17:49     ` Ian Rogers
2025-10-31 19:39 ` Namhyung Kim
2025-10-31 20:40   ` Tony Jones
2025-11-04  3:16     ` Namhyung Kim [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=aQlv-w0axiiMrZVD@google.com \
    --to=namhyung@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=tonyj@suse.de \
    /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 NNTP newsgroup(s).