[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimmScKO8YnPJWfTqFXBXQYwbbdej-gaYnHCgeTc@mail.gmail.com>
Date: Tue, 18 May 2010 11:36:52 +0200
From: Stephane Eranian <eranian@...gle.com>
To: tzanussi@...il.com
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org, mingo@...e.hu,
paulus@...ba.org, davem@...emloft.net, fweisbec@...il.com,
acme@...radead.org, perfmon2-devel@...ts.sf.net, eranian@...il.com,
Masami Hiramatsu <mhiramat@...hat.com>
Subject: [BUG] perf: record does not seem to store buildids anymore
Hi,
I am trying to understand how perf record deals with buildids.
I am interested in offline and not live processing. According
to http://lkml.org/lkml/2010/5/1/5, the inject patch does not
change perf record. It should still save the buildids at the
end of the perf.data file. I suspect it does not anymore.
If I do:
$ perf record -o - noploop 2 | perf inject -b | perf report -v -i -
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.063 MB - (~2756 samples) ]
build id event received for
/lib/modules/2.6.34-tip-default+/build/vmlinux:
0ad6b5dd1295e0177be9d12acafa72daac664ee7
Looking at the vmlinux_path (5 entries long)
Using /lib/modules/2.6.34-tip-default+/build/vmlinux for symbols
build id event received for /usr/local/bin/noploop:
e8a36c0c1e36e18522233ff2a4b1fff0f9689b1c
There is indeed a buildid generated for my noploop test program.
But I do the simpler:
$ perf record -o perf.out noploop 2
noploop for 2 seconds
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.063 MB perf.out (~2739 samples) ]
$ perf buildid-list -i perf.out
$
I get nothing.
If I try with perf report -D:
$ perf report -D -i perf.out
.....
TOTAL events: 2011
MMAP events: 21
LOST events: 0
COMM events: 1
EXIT events: 1
THROTTLE events: 0
UNTHROTTLE events: 0
FORK events: 0
READ events: 0
SAMPLE events: 1988
ATTR events: 0
EVENT_TYPE events: 0
TRACING_DATA events: 0
BUILD_ID events: 0
It shows no buildid events found.
So either something is broken or I don't understand the logic here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists