From: Stephane Eranian <eranian@google.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, paulus@samba.org, davem@davemloft.net,
robert.richter@amd.com, perfmon2-devel@lists.sf.net,
eranian@gmail.com
Subject: [BUG] perf: perf trace does not work anymore
Date: Thu, 29 Apr 2010 14:28:02 +0200 [thread overview]
Message-ID: <v2mbd4cb8901004290528jb13ced31j7f8b0231019bbbcb@mail.gmail.com> (raw)
Hi,
I am trying to use perf trace to dump the raw samples.
$ perf record -R noploop 5
noploop for 5 seconds
[ perf record: Woken up 3 times to write data ]
[ perf record: Captured and wrote 0.269 MB perf.data (~11759 samples) ]
$ perf trace
Fatal: reading input file (size expected=3 received=-1)
Seems like trace does not understand the format of the perf.data file anymore.
This used to work. Did you change the purpose of perf trace?
next reply other threads:[~2010-04-30 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 12:28 Stephane Eranian [this message]
2010-04-30 17:39 ` Frederic Weisbecker
2010-05-01 5:44 ` Tom Zanussi
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=v2mbd4cb8901004290528jb13ced31j7f8b0231019bbbcb@mail.gmail.com \
--to=eranian@google.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.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
all inboxes | Powered by JetHome®