From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Yuanfang Chen <cyfmxc@gmail.com>
Cc: linux-perf-users@vger.kernel.org, David Ahern <dsahern@gmail.com>
Subject: Re: address output in 'perf script' does not work for addr2line
Date: Tue, 3 Mar 2015 13:23:22 -0300 [thread overview]
Message-ID: <20150303162322.GK5187@kernel.org> (raw)
In-Reply-To: <CAJh9x3pz1aLQP_vvfN_Y_BwF4ekcU1mqvZFJz7x7X6QqLkK1jg@mail.gmail.com>
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?
I would argue that it would be even better if it resolved to file:lineno
by default...
- Arnaldo
> a.out 26620 [000] 314643.350007: 6825289 cycles:
> 57e main (/home/arch/Trash/a.out)
> 20800 __libc_start_main (/usr/lib/libc-2.21.so)
> 13d6258d4c544155 [unknown] ([unknown])
>
> thank you,
> Yuanfang
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-03 16:23 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 [this message]
2015-03-03 19:27 ` Yuanfang Chen
2015-03-03 19:54 ` David Ahern
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=20150303162322.GK5187@kernel.org \
--to=acme@kernel.org \
--cc=cyfmxc@gmail.com \
--cc=dsahern@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).