[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64da0019-4816-a409-be93-b1cf7021c584@huawei.com>
Date: Tue, 19 Jul 2022 16:24:42 +0100
From: John Garry <john.garry@...wei.com>
To: Josh Poimboeuf <jpoimboe@...nel.org>
CC: <keescook@...omium.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: faddr2line issue
On 14/07/2022 17:41, Josh Poimboeuf wrote:
> On Thu, Jul 14, 2022 at 10:57:51AM +0100, John Garry wrote:
>> On 08/07/2022 15:47, John Garry wrote:
>>
>> +
>>
>> JFYI, This issue is caused by CONFIG_DEBUG_INFO now being default off in my
>> .config from commit f9b3cd245784 ("Kconfig.debug: make DEBUG_INFO selectable
>> from a choice").
>>
>> By enabling that config faddr2line now looks ok again.
>>
>> BTW, Could we add a check for any kernel dependency in this tool?
> Hi John,
>
> The script doesn't know how to reliably find the .config file, but it
> should be able to check for missing DWARF in the binary itself.
Hi Josh,
So adding config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT to v5.19-rc2 got it
working again for me on arm64. However commit dcea997beed6 ("faddr2line:
Fix overlapping text section failures, the sequel") seems to be broken
for me, below - this first appeared in rc3. Any idea what the issue
could be?
$./faddr.sh hisi_sas_sata_done+0x8/0x38
hisi_sas_sata_done+0x8/0x38:
fs mm ??:0
Thanks,
John
Powered by blists - more mailing lists