From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Mark Hills <mark@pogo.org.uk>, Andi Kleen <andi@firstfloor.org>,
linux-perf-users@vger.kernel.org
Subject: Re: perf cannot see call graph, visible in gdb
Date: Mon, 9 Sep 2013 16:35:37 +0200 [thread overview]
Message-ID: <20130909143537.GA28036@krava.redhat.com> (raw)
In-Reply-To: <522DD5A5.70500@gmail.com>
On Mon, Sep 09, 2013 at 07:05:25AM -0700, David Ahern wrote:
> Adding Jiri.
>
> On 9/9/13 5:59 AM, Mark Hills wrote:
> >On Fri, 6 Sep 2013, Andi Kleen wrote:
> >
> >>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.
> >
> >Thank you, much appreciated.
> >
> >A newer perf appears to need a newer kernel too, and it's not practical
> >for me to break away from the RedHat kernel at the moment (currently on
> >2.6.32-358.14.1.el6)
>
> Any updates to RHEL6 for dwarf callchains?
>
unfortunately no news in RHEL6 for this one
jirka
prev parent reply other threads:[~2013-09-09 14:36 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
2013-09-09 12:59 ` Mark Hills
2013-09-09 14:05 ` David Ahern
2013-09-09 14:35 ` Jiri Olsa [this message]
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=20130909143537.GA28036@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--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 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).