From: Andi Kleen <andi@firstfloor.org>
To: mauro.andreolini@gmail.com
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Two questions on perf dwarf callchains
Date: Fri, 17 Jan 2014 12:11:53 -0800 [thread overview]
Message-ID: <87d2jq1i7q.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1389954083.1125.23.camel@nb-andreolini.mat.unimo.it> (Mauro Andreolini's message of "Fri, 17 Jan 2014 11:21:23 +0100")
Mauro Andreolini <mauro.andreolini@gmail.com> writes:
> file to get perf report to print the function names.
> Is this expected behaviour? How do I get perf to automatically extract
> symbols from compressed files?
Someone would need to write the code to do that I guess.
>
> To which function would 0x7facc1df12a0 match? It does not even seem to
> be in the mapped address space of "ls". I am clueless.
The unwinder got confused. A common cause is incomplete or partially
broken dwarf unwind information. May be a compiler problem.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-01-17 20:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 10:21 Two questions on perf dwarf callchains Mauro Andreolini
2014-01-17 20:11 ` Andi Kleen [this message]
2014-01-17 23:37 ` Mauro Andreolini
2014-01-18 4:42 ` Andi Kleen
2014-01-22 14:40 ` Mauro Andreolini
2014-01-22 17:55 ` Andi Kleen
2014-01-22 18:02 ` Mauro Andreolini
2014-01-29 11:18 ` Jiri Olsa
2014-01-29 15:09 ` Mauro Andreolini
2014-01-30 11:47 ` Jiri Olsa
2014-01-30 14:43 ` Mauro Andreolini
2014-01-30 15:40 ` Jiri Olsa
2014-02-03 14:30 ` Mauro Andreolini
2014-02-04 15:28 ` Mauro Andreolini
2014-02-04 15:35 ` Jiri Olsa
2014-02-04 16:01 ` Mauro Andreolini
2014-01-29 13:02 ` Mauro Andreolini
-- strict thread matches above, loose matches on Subject: below --
2014-01-17 23:42 Mauro Andreolini
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=87d2jq1i7q.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mauro.andreolini@gmail.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.