lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8046e5bb-06d4-47dd-ad08-deef63a7e734@t-8ch.de>
Date: Thu, 1 May 2025 08:59:39 +0200
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>, 
	Adrian Hunter <adrian.hunter@...el.com>, Ian Rogers <irogers@...gle.com>, 
	James Clark <james.clark@...aro.org>, Jiri Olsa <jolsa@...nel.org>, 
	Kan Liang <kan.liang@...ux.intel.com>, Ravi Bangoria <ravi.bangoria@....com>, 
	Joe Mario <jmario@...hat.com>, Namhyung Kim <namhyung@...nel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-perf-users@...r.kernel.org
Subject: Re: DW_AT_comp_dir and O= usage not working with objdump -dS, perf
 probe, etc

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@...ssschuh.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@...ssschuh.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ