From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: linux-perf-users@vger.kernel.org
Subject: profiling Firefox, no perf-<PID>.map file
Date: Sat, 03 Sep 2016 20:53:26 +0200 [thread overview]
Message-ID: <1472928806.2377.2.camel@suse.cz> (raw)
Hello,
when profiling firefox with perf (i.e. `perf top` or `perf record`) I
get errors like "Failed to open /tmp/perf-<PID>.map, continuing
without symbols". The perf docs says it has to do with the support for
JIT'ed code (tools/perf/Documentation/jit-interface.txt), which I
guess is produced by firefox' javascript engine (I could be wrong).
The documentation is a bit vague on how to have those perf-<PID>.map
files produced correctly, and the original commit introducing this
feature, 80d496be89ed "perf report: Add support for profiling JIT
generated code" only says "A JIT compiler is required [...]".
Is there a way to profile firefox and get those *.map files?
It's more of a curiosity, I am new to perf and I'm playing around.
Thanks,
Giovanni
next reply other threads:[~2016-09-03 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 18:53 Giovanni Gherdovich [this message]
2016-09-03 20:37 ` profiling Firefox, no perf-<PID>.map file Milian Wolff
2016-09-04 10:50 ` Giovanni Gherdovich
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=1472928806.2377.2.camel@suse.cz \
--to=ggherdovich@suse.cz \
--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).