linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sesse@google.com>
To: acme@kernel.org
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	irogers@google.com
Subject: Re: [PATCH v7 4/4] perf report: LLVM-based symbol listing
Date: Sun, 26 May 2024 23:24:40 +0200	[thread overview]
Message-ID: <ZlOomG5NacWlV_RY@google.com> (raw)
In-Reply-To: <20240526182212.544525-4-sesse@google.com>

On Sun, May 26, 2024 at 08:22:12PM +0200, Steinar H. Gunderson wrote:
> +
> +	symbols__fixup_end(dso__symbols(dso), false);
> +	symbols__fixup_duplicate(dso__symbols(dso));
> +	dso__set_adjust_symbols(dso, true);
> +	ret = 0;

Urgh, evidently I forgot to copy over dso->text_offset and dso->text_end
here, which I guess needs to happen.

Even after doing that, I still cannot annotate Windows symbols, though;
I get

  Couldn't annotate RtlLeaveCriticalSection:
  Internal error: Invalid -1 error code

This is true even with libbfd in a non-distro build (without any of my
LLVM patches), so there must be something else at play here.

I _can_ run a Windows binary in WINE and get the right symbols out with
perf report, though. So this leaves only demangling as the final piece
of the puzzle to make distro builds essentially equal to nondistro builds.

/* Steinar */

  reply	other threads:[~2024-05-26 21:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26 18:22 [PATCH v7 1/4] perf report: Support LLVM for addr2line() Steinar H. Gunderson
2024-05-26 18:22 ` [PATCH v7 2/4] perf annotate: split out read_symbol() Steinar H. Gunderson
2024-05-26 18:22 ` [PATCH v7 3/4] perf annotate: LLVM-based disassembler Steinar H. Gunderson
2024-05-29  4:06   ` Namhyung Kim
2024-06-02 20:38     ` Steinar H. Gunderson
2024-05-26 18:22 ` [PATCH v7 4/4] perf report: LLVM-based symbol listing Steinar H. Gunderson
2024-05-26 21:24   ` Steinar H. Gunderson [this message]
2024-05-29  4:11   ` Namhyung Kim
2024-06-02 20:39   ` Steinar H. Gunderson
2024-05-29  3:56 ` [PATCH v7 1/4] perf report: Support LLVM for addr2line() Namhyung Kim
2024-05-29 13:52   ` Arnaldo Carvalho de Melo
2024-05-30 16:55     ` Namhyung Kim
2024-05-30 16:58 ` Namhyung Kim
2024-06-02 20:37   ` Steinar H. Gunderson
2024-06-05  1:13     ` 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=ZlOomG5NacWlV_RY@google.com \
    --to=sesse@google.com \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).