Hi -
On Wed, Jun 17, 2015 at 04:11:47PM -0300, Ismael Garrido wrote:
> Attempting to extract kernel debuginfo build ID from
> /lib/modules/3.16.0-4-amd64/build/vmlinux.id
> Attempting to extract kernel debuginfo build ID from /sys/kernel/notes
> semantic error: while resolving probe point: identifier 'kernel' at
> <input>:1:7
> thrown from: elaborate.cxx:1062
> source: probe kernel.trace("*") {}
> ^
>
> semantic error: no match
> thrown from: elaborate.cxx:1025
> [...]
This seems similar to this report:
https://sourceware.org/ml/systemtap/2014-q4/msg00202.html
... which may be corrected by this upstream systemtap.git commit,
available in stap releases 2.7 and 2.8:
commit b19a43768009076de3aea638922dfaebb687e3e9
Author: Josh Stone <[email protected]>
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.
- FChE
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
