From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kim Phillips Subject: Re: Not finding symbol information Date: Mon, 5 Feb 2018 17:35:41 -0600 Message-ID: <20180205173541.ce7e8fdf3d4c9230a2a70c96@arm.com> References: <30C2D590D16A5C46ADFE65219103779892609BF7@AZ-US1EXMB02.global.avaya.com> <1590706.6giPFGD14k@milian-kdab2> <20180202183829.8ca5ac81d7c48bfafc7b79d1@arm.com> <30C2D590D16A5C46ADFE6521910377989260A050@AZ-US1EXMB02.global.avaya.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from foss.arm.com ([217.140.101.70]:59020 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750724AbeBEXfn (ORCPT ); Mon, 5 Feb 2018 18:35:43 -0500 In-Reply-To: <30C2D590D16A5C46ADFE6521910377989260A050@AZ-US1EXMB02.global.avaya.com> Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: "Vuille, Martin (Martin)" Cc: Milian Wolff , "linux-perf-users@vger.kernel.org" On Sat, 3 Feb 2018 03:30:02 +0000 "Vuille, Martin (Martin)" wrote: > BTW, I found some odd behaviour around that too. 'perf report --symfs PATH' is > looking for the buildid cache in 'PATH/$HOME/.debug', not '$HOME/.debug'. > Not sure whether that's design intent or a bug. Yeah, that doesn't sound right: the manpage just says "Look for files with symbols relative to this directory." > > It might also be worth trying running the report on the target, if possible. I'll > > try and take a look next week...I need to revive my > > arm32 boxes... > > Unfortunately the stripped binaries just barely fit on the target, so getting the > debug info on there is out of the question. OK, in that case can you try cherry-picking commit 9b200653518e "perf symbols: Take into account symfs setting when reading file build ID"? It looks highly relevant but I haven't been able to make sure yet. Thanks, Kim