Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <3492d341-a681-f344-f5cd-5b1ea3725f31@huawei.com>
Date:   Thu, 14 Jul 2022 10:57:51 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Subject: Re: faddr2line issue
From:   John Garry <john.garry@huawei.com>
To:     <jpoimboe@kernel.org>, <keescook@chromium.org>
CC:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <09df26a9-27af-1276-34c6-820bf7e27da8@huawei.com>
In-Reply-To: <09df26a9-27af-1276-34c6-820bf7e27da8@huawei.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

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?

Thanks,
John

> Hi Josh,
> 
> I am finding that for a few mainline kernel releases that faddr2line 
> does seem to be working:
> 
> ./scripts/faddr2line vmlinux  sas_discover_domain+0x4dc/0x560
> sas_discover_domain+0x4dc/0x560:
> fs mm ??:0
> 
> This is on my arm64 system. I have not tried another arch. Are there any 
> known issues?
> 
> Maybe I'm using it incorrectly... I can go back and see when this 
> stopped working for me.
> 
> Cheers,
> John