This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: SystemTap fails to find kernel tracepoints
- From: Josh Stone <jistone at redhat dot com>
- To: KDr2 <killy dot draw at gmail dot com>
- Cc: David Smith <dsmith at redhat dot com>, systemtap at sourceware dot org
- Date: Thu, 08 Jan 2015 15:00:53 -0800
- Subject: Re: SystemTap fails to find kernel tracepoints
- Authentication-results: sourceware.org; auth=none
- References: <CAHfjm6gvwwdCKEjf+pAczYW37S5wg8m=EzpitFvZbj8yke5a=Q at mail dot gmail dot com> <5485C8EE dot 6090708 at redhat dot com> <5486524F dot 7020207 at redhat dot com> <CAHfjm6iFMeQVermwGMbr5kSXUQnkJgnj4iQuxijhRFy6KoddNw at mail dot gmail dot com> <CAHfjm6hMRyxfq5uC+d-ULDYa7g8_a7djH270X3dGS7FzQ5t8Gw at mail dot gmail dot com>
On 12/08/2014 08:29 PM, KDr2 wrote:
> But, will stap support the kernel built in a separate dir?
I just pushed this:
commit b19a43768009076de3aea638922dfaebb687e3e9
Author: Josh Stone <jistone@redhat.com>
Date: Thu Jan 8 14:47:20 2015 -0800
Use the kernel source symlink for tracepoints
When the source symlink is different than the build symlink, as for
out-of-tree kernel builds and Debian linux-headers, then we should use
that path as a prefix for finding tracepoint headers.
I tested it with Debian's kernel, but I would appreciate your feedback
whether it also solves your out-of-tree kernel builds.
Thanks!
Josh