linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taeung Song <treeze.taeung@gmail.com>
To: Mark Davis <markdavisinboston@gmail.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: Missing stack symbols with perf_event's perf report, despite -fno-omit-frame-pointer compilation
Date: Tue, 19 Apr 2016 11:26:17 +0900	[thread overview]
Message-ID: <57159749.9060705@gmail.com> (raw)
In-Reply-To: <loom.20160419T015612-712@post.gmane.org>

Hi,

On 04/19/2016 09:07 AM, Mark Davis wrote:
> I'm struggling getting perf_events to give me stack traces with symbols,
> despite reading many tutorials on the subject and doing (I think) all the
> necessary things. It's possible that my local install of perf (details on that
> below) is somehow botched? Anyway, here's what I did:
>
> main.cpp is a simple C++ program that calls a few functions defined in the same
> file, allocates some memory and frees it, and prints a few things out.
>
> compilation command:
>
>      gcc -std=c++11 -lstdc++ main.cpp -Og -fno-omit-frame-pointer -fno-inline -o
> arr_test
>
> profile command:
>
>      perf record -a -g -- ./arr_test && perf report --stdio
>
>
> I do get the following warnings about kernel symbols, but I don't think this
> should matter given that I only care about symbols in my application for now:
>

As a guide..
If you add ":u" to a event name, you can measure only at the user level e.g.

     perf record -ag -e cycles:u ./arr_test

      parent reply	other threads:[~2016-04-19  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  0:07 Missing stack symbols with perf_event's perf report, despite -fno-omit-frame-pointer compilation Mark Davis
2016-04-19  0:18 ` David Ahern
2016-04-25  9:01   ` Milian Wolff
2016-04-26  1:03     ` Arnaldo Carvalho de Melo
2016-04-19  2:26 ` Taeung Song [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=57159749.9060705@gmail.com \
    --to=treeze.taeung@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=markdavisinboston@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 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).