Received: by 10.223.185.111 with SMTP id b44csp657634wrg; Fri, 9 Mar 2018 11:08:30 -0800 (PST) X-Google-Smtp-Source: AG47ELuR75v5vobvNQ462TZn09MfZIOR+C0lPyCyOW6NRhu/SpDdOeW1uL9xzyJ7g0GBEIFRbJ3d X-Received: by 10.101.83.194 with SMTP id z2mr25125955pgr.133.1520622510145; Fri, 09 Mar 2018 11:08:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520622510; cv=none; d=google.com; s=arc-20160816; b=RhVn9IXxmx/rh5LSQBAaRdK8wumnXWb78sZprFp3YGjn91oPyLlXtoQMDnZMZFqkQH brNlRqNDzmGf1as/0Ki5MsUnuiRHmebdskrjCNWEKsYu72yd4sX9qqgRCIAwCSxCsq6F 2MIgJyL2ISBdAaig8wn4ynX+CyvCVl15A1CeiHWHT05jfkEvtU7xssP3/AQINA9dZY86 k9ZATt3iLVpthHb3OJ9qg3xTZlETm4lgUcYGWWscI4/vowga703lmDJjsxpa2cwbspqF m+vetsGy+pVxPTOHZiWPmHCBliDgm89uXJJ4Nx/paIwwU6vkSke8Nbf/JfCy/sW19rOr Zi8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:arc-authentication-results; bh=sRIfWKg+b5N+kpb8PDpXrCK+jwz6Unq9smMl7NwEsBE=; b=fielgmEulDIfJA/IZk6BR7yf3+atz52uXaHbqYtSsuhBo1Kem7J7nJVKr8PFdNsgFK /o9wMZ2TFdlWICGX4hoCOo8xuUFXrjsaWWL0cYXe3FuH7yfPsaxX0pM3NOAvGRa57JhX amsoqYf4NTEsljF7NYn0hnxblSErWDr4VaLVYwYGYHj57FHxxlCUj3hkeVcomvuc6Slu HZ2PK03Ms1pNyY45n6qabga21w7MpbTx85a5walalT4Gn98VvoV/mQS5QRR9QikHcLOA fZ8LQ2urNzPYXoPf3BpdJ+7dDpzjcY71ru70aBS9cW9ACY9vcUE+uGxyGjpIeYocn90y 2bSA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s6-v6si1337761plq.382.2018.03.09.11.08.15; Fri, 09 Mar 2018 11:08:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932358AbeCITHT (ORCPT + 99 others); Fri, 9 Mar 2018 14:07:19 -0500 Received: from mail.kernel.org ([198.145.29.99]:41838 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751205AbeCITHS (ORCPT ); Fri, 9 Mar 2018 14:07:18 -0500 Received: from jouet.infradead.org (unknown [190.15.121.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0D233206B2; Fri, 9 Mar 2018 19:07:18 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0D233206B2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=acme@kernel.org Received: by jouet.infradead.org (Postfix, from userid 1000) id D320E1450F2; Fri, 9 Mar 2018 16:07:15 -0300 (-03) Date: Fri, 9 Mar 2018 16:07:15 -0300 From: Arnaldo Carvalho de Melo To: Martin Vuille Cc: Arnaldo Carvalho de Melo , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] perf annotate: Don't prepend symfs path to build_id_filename Message-ID: <20180309190715.GB25111@kernel.org> References: <20180211191937.9703-1-jpmv27@aim.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180211191937.9703-1-jpmv27@aim.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Sun, Feb 11, 2018 at 02:19:37PM -0500, Martin Vuille escreveu: > build_id_filename already contains symfs path if applicable, so > don't prepend it a second time. Where is the analysis that shows that that is the case? I looked here at the implementation for dso__build_id_filename() and couldn't find where was it that the symfs would be appended, can you clarify? - Arnaldo > Signed-off-by: Martin Vuille > --- > tools/perf/util/annotate.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c > index 28b233c3dcbe..425b7f0760ec 100644 > --- a/tools/perf/util/annotate.c > +++ b/tools/perf/util/annotate.c > @@ -1381,7 +1381,7 @@ static int dso__disassemble_filename(struct dso *dso, char *filename, size_t fil > > build_id_filename = dso__build_id_filename(dso, NULL, 0, false); > if (build_id_filename) { > - __symbol__join_symfs(filename, filename_size, build_id_filename); > + scnprintf(filename, filename_size, "%s", build_id_filename); > free(build_id_filename); > } else { > if (dso->has_build_id) > -- > 2.13.6