Em Thu, Jun 03, 2010 at 03:06:13PM -0300, Arnaldo Carvalho de Melo escreveu:
[root@emilia ~]# mv /lib/modules/2.6.35-rc1/build/vmlinux /lib/modules/2.6.35-rc1/build/vmlinux.OFF
[root@emilia ~]# perf annotate -vvv memcpy > /dev/null
build id event received for [kernel.kallsyms]: 310920b54cbbf242dbfa09052f652806d2c73821
build id event received for /lib64/libtinfo.so.5.7: cd9da7b5b1fcb25ee6b3762bb9fe62f782590fd5
Looking at the vmlinux_path (6 entries long)
No build_id in /root/.debug/.build-id/31/0920b54cbbf242dbfa09052f652806d2c73821, ignoring it
No build_id in vmlinux, ignoring it
No build_id in /boot/vmlinux, ignoring it
No build_id in /boot/vmlinux-2.6.35-rc1, ignoring it
No build_id in /lib/modules/2.6.35-rc1/build/vmlinux, ignoring it
No build_id in /usr/lib/debug/lib/modules/2.6.35-rc1/vmlinux, ignoring it
Using /proc/kallsyms for symbols
[root@emilia ~]#
[root@emilia ~]# vi ~/.perfconfig
[root@emilia ~]# cat ~/.perfconfig
[tui]
report = on
annotate = off
[root@emilia ~]# perf annotate memcpy
[root@emilia ~]# perf annotate memcpy
[root@emilia ~]# perf annotate -k vmlinux memcpy
[kernel.kallsyms] with build id 310920b54cbbf242dbfa09052f652806d2c73821 not found, continuing without symbols
Yeah, these error messages suckz, will work on having proper messages
for these cases :-\
- Arnaldo
--