From: David Ahern <dsahern@gmail.com>
To: Martin Rosenberg <mrosenberg@mozilla.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: perf report does not get along with perf record -A
Date: Mon, 25 Jun 2012 22:40:49 -0600 [thread overview]
Message-ID: <4FE93D51.7090709@gmail.com> (raw)
In-Reply-To: <443195725.4576626.1340669457668.JavaMail.root@mozilla.com>
On 6/25/12 6:10 PM, Martin Rosenberg wrote:
> I'm working under the assumption that if I want to collect statistics from multiple runs of a program, I can do this by running
> perf record prog; perf record -A prog; perf record -A prog
>
> I've found that running perf record twice results in perf report hanging, and running it more than twice results in perf report first spewing a message about invalid formats, then crashing.
> A log of the session, as well as the binary, its input and perf.data can be found at:
What does 'perf --version' show?
David
next prev parent reply other threads:[~2012-06-26 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1974638847.4574239.1340667841898.JavaMail.root@mozilla.com>
2012-06-26 0:10 ` perf report does not get along with perf record -A Martin Rosenberg
2012-06-26 4:40 ` David Ahern [this message]
2012-06-26 5:04 ` Martin Rosenberg
2012-06-26 14:24 ` David Ahern
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=4FE93D51.7090709@gmail.com \
--to=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrosenberg@mozilla.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).