linux-kernel.vger.kernel.org archive mirror
 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: Tue, 19 Jul 2022 16:24:42 +0100	[thread overview]
Message-ID: <64da0019-4816-a409-be93-b1cf7021c584@huawei.com> (raw)
In-Reply-To: <20220714164136.n2ycc5axt7vtctgs@treble>

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

  reply	other threads:[~2022-07-19 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 14:47 faddr2line issue John Garry
2022-07-14  9:57 ` John Garry
2022-07-14 16:41   ` Josh Poimboeuf
2022-07-19 15:24     ` John Garry [this message]
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

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=64da0019-4816-a409-be93-b1cf7021c584@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;
as well as URLs for NNTP newsgroup(s).