From: Francis Moreau <francis.moro@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: vmlinux buildid doesn't match the running one (/sys/kernel/notes)
Date: Thu, 28 Apr 2011 19:04:13 +0200 [thread overview]
Message-ID: <BANLkTim+kr6TYdkuh=bugJaNmSnLE0h-8Q@mail.gmail.com> (raw)
Hello,
I'm trying to use perf-probe, but it fails.
Basically it's due to the buildid of the running kernel (the one which
can be read from /sys/kernel/notes) and the one in vmlinx (which I
compiled my self).
I did this:
$ make
$ make modules_install install
$ ls vmlinux
vmlinux
reboot
$ perf probe -k vmlinux -L schedule
Failed to find path of kernel module.
Failed to open debuginfo file.
Error: Failed to show lines. (-2)
So my question is why the buildids doesn't match ?
I guess I did something wrong since it's pretty a standard use case
but I don't see why...
Thanks
--
Francis
next reply other threads:[~2011-04-28 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 17:04 Francis Moreau [this message]
2011-05-01 19:02 ` vmlinux buildid doesn't match the running one (/sys/kernel/notes) Francis Moreau
[not found] ` <BANLkTikauRD6CF3MuBmuvQqJAuDPHE2x-Q@mail.gmail.com>
2011-05-04 13:12 ` Lin Ming
2011-05-05 9:41 ` Francis Moreau
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='BANLkTim+kr6TYdkuh=bugJaNmSnLE0h-8Q@mail.gmail.com' \
--to=francis.moro@gmail.com \
--cc=linux-perf-users@vger.kernel.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).