Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756213AbbFPOe3 (ORCPT ); Tue, 16 Jun 2015 10:34:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41614 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754791AbbFPOeU (ORCPT ); Tue, 16 Jun 2015 10:34:20 -0400 Date: Tue, 16 Jun 2015 11:34:01 -0300 From: Arnaldo Carvalho de Melo To: Stephane Eranian Cc: LKML , Jiri Olsa , Namhyung Kim , David Ahern , Peter Zijlstra , "mingo@elte.hu" Subject: Re: [BUG] perf report: fails to symbolize when vaddr is non zero for shared objects Message-ID: <20150616143401.GA2548@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1210 Lines: 33 Em Tue, Jun 16, 2015 at 12:03:01AM -0700, Stephane Eranian escreveu: > Hi, > > It has been brought to my attention that on systems where the text > of shared libs is not loaded with a zero virtual address, perf report > fails to symbolize > correctly samples. This is true of older versions of perf and also the latest > in tip.git. > > I looked at symbol-elf.c and I did not see a place where the vaddr was taken > into account from the program headers in the case of ET_DYN. I see it for > ET_EXE, though. > > $ readelf -e lib.so > Type: DYN (Shared object file) > .... > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align > LOAD 0x000000 0x0000d000 0x0000d000 0x73657c 0x73657c R E 0x1000 > > If you get samples in the shared lib, they will be off, possibly > attributed to the wrong > functions. > > Could this be fixed quickly? You tell me, do you have a patch to propose? :-) - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/