From: Milian Wolff <milian.wolff@kdab.com>
To: Giovanni Gherdovich <ggherdovich@suse.cz>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: profiling Firefox, no perf-<PID>.map file
Date: Sat, 03 Sep 2016 22:37:55 +0200 [thread overview]
Message-ID: <3432177.9qbfN6MEYg@agathebauer> (raw)
In-Reply-To: <1472928806.2377.2.camel@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Samstag, 3. September 2016 20:53:26 CEST Giovanni Gherdovich wrote:
> 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.
You need integration for generating such a file in the JavaScript engine. node
and QML are two examples for that. But if you don't want to attribute JIT code
addresses to JavaScript code, you can safely ignore this warning.
Bye
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-09-03 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 18:53 profiling Firefox, no perf-<PID>.map file Giovanni Gherdovich
2016-09-03 20:37 ` Milian Wolff [this message]
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=3432177.9qbfN6MEYg@agathebauer \
--to=milian.wolff@kdab.com \
--cc=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).