From: Han Pingtian <phan@redhat.com>
To: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: perf archive warning
Date: Wed, 2 Mar 2011 12:23:54 +0800 [thread overview]
Message-ID: <20110302042354.GB5186@hpt.nay.redhat.com> (raw)
Hi,
perf archive has some waring messages, is this a bug?
root@intel-s3e36-01 perf]# ./perf-archive
tar: .build-id/b2/370e39ea2898c6e11c188e2f3879e4e3d6d1ef: Cannot stat: No such file or directory
tar: .build-id/b2/370e39ea2898c6e11c188e2f3879e4e3d6d1ef: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
Now please run:
$ tar xvf perf.data.tar.bz2 -C ~/.debug
wherever you need to run 'perf report' on.
[root@intel-s3e36-01 perf]# ./perf --version
perf version 2.6.38.rc6.166.g493f33
[root@intel-s3e36-01 perf]# ./perf buildid-list
b2370e39ea2898c6e11c188e2f3879e4e3d6d1ef [kernel.kallsyms]
dd95cb496ebc4ed922eeb5640965f1243fcfcd9a /lib/modules/2.6.32-118.el6.x86_64/kernel/fs/ext4/ext4.ko
9e1aca88b83308cec7574d74975fa6f7d654c96e /lib64/libc-2.12.so
d880be15bf992b5fbcc629e6bbf1c747a928ddd5 /lib64/libglib-2.0.so.0.2200.5
d1b2ca4e1ec8f81ba820e5f1375d960107ac7e50 /usr/lib64/libstdc++.so.6.0.13
[root@intel-s3e36-01 perf]#
--
Han Pingtian
Quality Engineer
hpt @ #kernel-qe
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
next reply other threads:[~2011-03-02 4:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 4:23 Han Pingtian [this message]
[not found] ` <AANLkTim+Ls+_cbHnMzdfWAWUj0Wx2rQtnoTCjZJ8Cnro@mail.gmail.com>
2011-03-02 8:29 ` perf archive warning Lin Ming
2011-03-02 8:53 ` Han Pingtian
2011-03-03 0:38 ` Lin Ming
2011-03-03 4:21 ` Han Pingtian
2011-03-03 4:21 ` Lin Ming
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=20110302042354.GB5186@hpt.nay.redhat.com \
--to=phan@redhat.com \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=peterz@infradead.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).