From: John Garry <john.garry@huawei.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: <keescook@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: faddr2line issue
Date: Wed, 20 Jul 2022 09:39:42 +0100 [thread overview]
Message-ID: <3bd9817d-1959-c081-e5d0-8b0e70b3f41e@huawei.com> (raw)
In-Reply-To: <20220720000654.yospyvbrfliy3lrn@treble>
On 20/07/2022 01:06, Josh Poimboeuf wrote:
>> 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
> Hm, what does faddr.sh do?
ah, it's just a wrapper to call scripts/faddr2line with vmlinux and $1
(being hisi_sas_sata_done+0x8/0x38, above) args
> Does addr2line also fail?
faddr2line fails, as below.
>
> Can you run
>
> bash -x scripts/faddr2line <vmlinux or .ko file> hisi_sas_sata_done+0x8/0x38
>
> and share the output?
on rc3 we get:
https://raw.githubusercontent.com/hisilicon/kernel-dev/private-topic-sas-5.19-faddr2line-linux-rc3/before2
With dcea997beed6 reverted on rc3:
https://raw.githubusercontent.com/hisilicon/kernel-dev/private-topic-sas-5.19-faddr2line-linux-rc3/after2
This is my branch is you want to see what I have:
https://github.com/hisilicon/kernel-dev/commits/private-topic-sas-5.19-faddr2line-linux-rc3
Thanks,
John
next prev parent reply other threads:[~2022-07-20 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 14:47 John Garry
2022-07-14 9:57 ` John Garry
2022-07-14 16:41 ` Josh Poimboeuf
2022-07-19 15:24 ` John Garry
2022-07-20 0:06 ` Josh Poimboeuf
2022-07-20 8:39 ` John Garry [this message]
2022-07-20 23:32 ` Josh Poimboeuf
2022-07-21 15:03 ` John Garry
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=3bd9817d-1959-c081-e5d0-8b0e70b3f41e@huawei.com \
--to=john.garry@huawei.com \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®