From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Paul Mackerras" <paulus@samba.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Tom Zanussi" <tzanussi@gmail.com>
Subject: Re: [GIT PULL 0/2] perf session fix host_machine handling wrt build ids
Date: Thu, 20 May 2010 11:29:31 -0300 [thread overview]
Message-ID: <20100520142931.GC26284@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTin1Lof5-907Afc24Ato1MqOE93uyxb-xx4XEYUg@mail.gmail.com>
Em Thu, May 20, 2010 at 11:54:17AM +0200, Stephane Eranian escreveu:
> Arnaldo,
>
> On Wed, May 19, 2010 at 7:01 PM, Arnaldo Carvalho de Melo
> <acme@infradead.org> wrote:
> > [root@doppio linux-2.6-tip]#
> > [root@doppio linux-2.6-tip]# perf archive
> > Now please run:
> >
> > $ tar xvf perf.data.tar.bz2 -C ~/.debug
> >
> > wherever you need to run 'perf report' on.
>
> Supposedly, on the remote machine with the perf.data +tarball files,
> I should be able to run perf report, perf annotate.
>
> I tried that. The perf report works but not perf annotate. It can't
> find the binary image of my program. Yet there is a copy in the
> .debug subdir. It seems, it is looking for the image using the
> absolute file path in perf.data, instead.
>
> Am I missing something here?
No, you are not, annotate should look by build-id, then pass this to
objdump, lemme cook a patch.
- Arnaldo
prev parent reply other threads:[~2010-05-20 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 17:01 [GIT PULL 0/2] perf session fix host_machine handling wrt build ids Arnaldo Carvalho de Melo
2010-05-19 17:01 ` [PATCH 1/2] perf symbols: Don't try to read the build-id twice Arnaldo Carvalho de Melo
2010-05-19 17:01 ` [PATCH 2/2] perf session: Make read_build_id routines look at the host_machine too Arnaldo Carvalho de Melo
2010-05-19 19:36 ` [GIT PULL 0/2] perf session fix host_machine handling wrt build ids Stephane Eranian
2010-05-19 20:11 ` Arnaldo Carvalho de Melo
2010-05-19 20:55 ` Stephane Eranian
2010-05-20 14:23 ` Arnaldo Carvalho de Melo
2010-05-20 4:14 ` Tom Zanussi
2010-05-20 9:54 ` Stephane Eranian
2010-05-20 14:29 ` Arnaldo Carvalho de Melo [this message]
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=20100520142931.GC26284@ghostprotocols.net \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tzanussi@gmail.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).