From: Andi Kleen <andi@firstfloor.org>
To: Mark Hills <mark@pogo.org.uk>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf cannot see call graph, visible in gdb
Date: Fri, 06 Sep 2013 12:49:34 -0700 [thread overview]
Message-ID: <87ioydhgs1.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1309051629550.29229@wes.ijneb.com> (Mark Hills's message of "Thu, 5 Sep 2013 17:48:07 +0100 (BST)")
Mark Hills <mark@pogo.org.uk> writes:
> I have a pre-compiled .so library, which was given to me for profiling.
>
> gdb can see a complete call stack -- both the library and my own code, as
> expected.
>
> But in perf the callgraph for the library is not present. I'm using "perf
> record -g", and the callgraph for the other code is seen.
>
> In what cases could gdb see the stack, but perf cannot?
No frame pointer.
Recompile with -fno-omit-frame-pointer
Or if you have a new enough perf, you can use -g dwarf to enable
dwarf backtracing, but it's very slow and also doesn't handle all
situations gdb handles.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-09-06 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 16:48 perf cannot see call graph, visible in gdb Mark Hills
2013-09-06 19:49 ` Andi Kleen [this message]
2013-09-09 12:59 ` Mark Hills
2013-09-09 14:05 ` David Ahern
2013-09-09 14:35 ` Jiri Olsa
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=87ioydhgs1.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark@pogo.org.uk \
/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.