mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Thu, 21 Jul 2022 16:03:05 +0100	[thread overview]
Message-ID: <f75a791e-7319-875e-04e4-9f30aa6f8606@huawei.com> (raw)
In-Reply-To: <20220720233243.lyjrhi43bwaxecm3@treble>

On 21/07/2022 00:32, Josh Poimboeuf wrote:
> On Wed, Jul 20, 2022 at 09:39:42AM +0100, John Garry wrote:
>> 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
> 
> Does this fix it?
> 
> diff --git a/scripts/faddr2line b/scripts/faddr2line
> index 94ed98dd899f..57099687e5e1 100755
> --- a/scripts/faddr2line
> +++ b/scripts/faddr2line
> @@ -112,7 +112,9 @@ __faddr2line() {
>   	# section offsets.
>   	local file_type=$(${READELF} --file-header $objfile |
>   		${AWK} '$1 == "Type:" { print $2; exit }')
> -	[[ $file_type = "EXEC" ]] && is_vmlinux=1
> +	if [[ $file_type = "EXEC" ]] || [[ $file_type == "DYN" ]]; then
> +		is_vmlinux=1
> +	fi
>   
>   	# Go through each of the object's symbols which match the func name.
>   	# In rare cases there might be duplicates, in which case we print all
> .

Yeah, looks ok now.

Tested-by: John Garry <john.garry@huawei.com>

thanks

      reply	other threads:[~2022-07-21 15:03 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
2022-07-20 23:32           ` Josh Poimboeuf
2022-07-21 15:03             ` John Garry [this message]

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=f75a791e-7319-875e-04e4-9f30aa6f8606@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®