All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "James Clark" <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v4 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing
Date: Mon, 09 Nov 2026 13:56:33 +0000	[thread overview]
Message-ID: <sashiko-outbox-205042@kernel.org> (raw)
In-Reply-To: <20261109-james-perf-test-fixes-v4-1-355ee6b81917@linaro.org>

> libdw__addr2line() finds the CU with dwfl_module_getsrc() and
> dwfl_module_addrdie(), which use dwarf_getaranges(). In elfutils 0.190
> this only reads .debug_aranges, which can be partial. For example, when
> Perf is built with LLVM=1, clang doesn't emit .debug_aranges by default
> so the lookup then fails and no source lines are found for most of the
> Perf binary.
> 
> This used to be hidden by falling back to the next addr2line style, but
> now missing information stops the fallback since commit (62d7cdc8d587
> "perf libdw: Optimize fallback logic for missing DWARF").
> 
> find_cu_die() in annotate-data.c already handles partial aranges by
> iterating all CUs in .debug_info and checking them with dwarf_haspc().
> Move it to dwarf-aux.c, then look up the line in that CU with
> dwarf_getsrc_die() and use the same CU for unwinding inlines. While
> [ ... ]
>   ---- end(-1) ----
>    79: test addr2line inline unwinding : FAILED!
> 
> Fixes: 88c51002d06f ("perf addr2line: Add a libdw implementation")
> Signed-off-by: James Clark <james.clark@linaro.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-james-perf-test-fixes-v4-0-355ee6b81917@linaro.org?part=1


  reply	other threads:[~2026-11-09 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 13:48 [PATCH v4 0/4] perf tools: LLVM dwarf and flaky test fixes James Clark
2026-11-09 13:48 ` [PATCH v4 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing James Clark
2026-11-09 13:56   ` sashiko-bot [this message]
2026-11-09 13:48 ` [PATCH v4 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables James Clark
2026-11-09 13:54   ` sashiko-bot
2026-11-09 13:48 ` [PATCH v4 3/4] perf test probe_vfs_getname: Fix missing debuginfo detection James Clark
2026-11-09 13:52   ` sashiko-bot
2026-11-09 13:48 ` [PATCH v4 4/4] perf test: Don't starve per-process tests with system-wide events James Clark
2026-11-09 13:57   ` sashiko-bot
2026-11-09 17:47   ` Ian Rogers
2026-11-10 12:30     ` James Clark
2026-11-10 16:49       ` Ian Rogers
2026-11-11 13:49         ` James Clark
2026-11-09 18:20 ` [PATCH v4 0/4] perf tools: LLVM dwarf and flaky test fixes Ian Rogers
2026-11-10 21:57   ` Namhyung Kim
2026-11-11 19:09 ` (subset) " Namhyung Kim

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=sashiko-outbox-205042@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=james.clark@linaro.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.