From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Joe Mario <jmario@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: DW_AT_comp_dir and O= usage not working with objdump -dS, perf probe, etc
Date: Thu, 1 May 2025 08:59:39 +0200 [thread overview]
Message-ID: <8046e5bb-06d4-47dd-ad08-deef63a7e734@t-8ch.de> (raw)
In-Reply-To: <aBKziq9dr_EsWLuZ@x1>
Hi Arnaldo,
On 2025-04-30 20:34:34-0300, Arnaldo Carvalho de Melo wrote:
> I noticed recently while testing some other patches that
> disassembling with objdump -dS didn't work when building the kernel with
> O= as it sets it to the build dir, not to where the sources are, for
> instance:
<snip>
> I haven't checked, ran out of time today, but I think this may be
> involved:
>
> commit 97282e6d380db8a07120fe1b794ac969ee4a3b5c
> Author: Thomas Weißschuh <linux@weissschuh.net>
> Date: Sat Mar 22 10:03:16 2025 +0100
>
> x86: drop unnecessary prefix map configuration
It should be caused by this one:
commit cacd22ce69585a91c386243cd662ada962431e63
Author: Thomas Weißschuh <linux@weissschuh.net>
Date: Sat Mar 15 14:20:14 2025 +0100
kbuild: make all file references relative to source root
There is already another report about objdump here:
https://lore.kernel.org/lkml/aBEttQH4kimHFScx@intel.com/
Let's continue the discussion there.
Thomas
next prev parent reply other threads:[~2025-05-01 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 23:34 Arnaldo Carvalho de Melo
2025-05-01 6:59 ` Thomas Weißschuh [this message]
2025-05-02 16:33 ` Arnaldo Carvalho de Melo
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=8046e5bb-06d4-47dd-ad08-deef63a7e734@t-8ch.de \
--to=linux@weissschuh.net \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.com \
/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
all inboxes | Powered by JetHome®