linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Yuanfang Chen <cyfmxc@gmail.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-perf-users@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: address output in 'perf script' does not work for addr2line
Date: Tue, 03 Mar 2015 12:54:26 -0700	[thread overview]
Message-ID: <54F61172.4050002@gmail.com> (raw)
In-Reply-To: <CAJh9x3rwvAdjXJ67wvNjWjy451zWy1a_7JjDKQacJkwWWL031A@mail.gmail.com>

On 3/3/15 12:27 PM, Yuanfang Chen wrote:
> On Tue, Mar 3, 2015 at 11:23 AM, Arnaldo Carvalho de Melo
> <arnaldo.melo@gmail.com> wrote:
>> Em Tue, Mar 03, 2015 at 11:07:18AM -0500, Yuanfang Chen escreveu:
>>> I'm using perf 3.19.0 on Archlinux
>>>
>>> [arch@t440s-arch ~/Trash]$ uname -a
>>> Linux t440s-arch 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET
>>> 2015 x86_64 GNU/Linux
>>>
>>> Recently after updating perf package, I found the 'ip' in 'perf
>>> script' like below is shorter than before. Also feeding that address
>>> (like 57e below) to addr2line does not output filename:lineno
>>> information anymore.  How do I fix this issue? Is this a bug?
>>
>> Yeah, I tried using it with addr2line and it didn't work :-\ So what
>> you're saying is that in the past it worked like that?
>>
>> If so, could you please 'git bisect' it to find out when it got broken?
>
> Yeah, it worked in the past.
> commit 5550171b2a9f8df26ff483051d060db06376b26d  change ip into
> relative address ( not sure relative to which address), which makes
> addr2line unable to parse.
>

That's Andi's commit.

  reply	other threads:[~2015-03-03 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 16:07 address output in 'perf script' does not work for addr2line Yuanfang Chen
2015-03-03 16:23 ` Arnaldo Carvalho de Melo
2015-03-03 19:27   ` Yuanfang Chen
2015-03-03 19:54     ` David Ahern [this message]
2015-03-03 20:50       ` Arnaldo Carvalho de Melo
2015-03-03 21:07         ` Arnaldo Carvalho de Melo
2015-03-06 23:19         ` Andi Kleen

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=54F61172.4050002@gmail.com \
    --to=dsahern@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=cyfmxc@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).