From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Wangnan (F)" <wangnan0@huawei.com>
Cc: Anton Blanchard <anton@au1.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf symbols: Fix annotation of objects with debuginfo files
Date: Mon, 15 Aug 2016 16:48:11 -0300 [thread overview]
Message-ID: <20160815194811.GC20972@kernel.org> (raw)
In-Reply-To: <57B16BAB.2010003@huawei.com>
Em Mon, Aug 15, 2016 at 03:13:47PM +0800, Wangnan (F) escreveu:
>
>
> On 2016/8/13 9:55, Anton Blanchard wrote:
> > From: Anton Blanchard <anton@samba.org>
> >
> > Commit 73cdf0c6ea9c ("perf symbols: Record text offset in dso
> > to calculate objdump address") started storing the offset of
> > the text section for all DSOs:
> >
> > if (elf_section_by_name(elf, &ehdr, &tshdr, ".text", NULL))
> > dso->text_offset = tshdr.sh_addr - tshdr.sh_offset;
> >
> > Unfortunately this breaks debuginfo files, because we need to calculate
> > the offset of the text section in the associated executable file. As a
> > result perf annotate returns junk for all debuginfo files.
> >
> > Fix this by using runtime_ss->elf which should point at the executable
> > when parsing a debuginfo file.
> >
> > Cc: stable@vger.kernel.org # v4.6+
> > Fixes: 73cdf0c6ea9c ("perf symbols: Record text offset in dso to calculate objdump address")
> > Signed-off-by: Anton Blanchard <anton@samba.org>
>
> I don't quite understand the debuginfo problem. I tested
> this patch follow steps recorded in commit 99e87f7 and
> see no problem.
>
> Tested-by: Wang Nan <wangnan0@huawei.com>
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2016-08-15 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 6:35 [PATCH] perf symbols: Fix annotation of objects with debuginfo files Anton Blanchard
2016-08-12 13:00 ` Arnaldo Carvalho de Melo
2016-08-12 16:47 ` Naveen N. Rao
2016-08-13 1:55 ` [PATCH v2] " Anton Blanchard
2016-08-14 16:56 ` Naveen N. Rao
2016-08-15 7:13 ` Wangnan (F)
2016-08-15 16:46 ` Naveen N. Rao
2016-08-15 19:48 ` Arnaldo Carvalho de Melo [this message]
2016-08-16 18:15 ` [tip:perf/urgent] " tip-bot for Anton Blanchard
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=20160815194811.GC20972@kernel.org \
--to=acme@kernel.org \
--cc=anton@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=wangnan0@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.