> I have just tested with the systemtap 2.9 package presently in xenial,
> and the following test case fails the same way there as with systemtap
> 2.3 in trusty:
>
> # stap -v -e 'probe vfs.read {printf("read performed\n"); exit()}'
> [...]
> semantic error: while resolving probe point: identifier 'kernel' at /usr/share/systemtap/tapset/linux/vfs.stp:882:18
> source: probe vfs.read = kernel.function("vfs_read")
> ^
>
> [...]
> Pass 2: analysis failed. [man error::pass2]
> Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
>
> It does not appear that an update to a newer systemtap version is going
> to be of any use on 14.04.
> [...]
This message indicates not something wrong with systemtap, but
something wrong with the installation of kernel debugging symbols.
(See also the error::pass2 man page and the given README.Debian file.)
Hi -
> I have just tested with the systemtap 2.9 package presently in xenial, systemtap/ tapset/ linux/vfs. stp:882: 18 function( "vfs_read" ) doc/systemtap/ README. Debian should help you get started.
> and the following test case fails the same way there as with systemtap
> 2.3 in trusty:
>
> # stap -v -e 'probe vfs.read {printf("read performed\n"); exit()}'
> [...]
> semantic error: while resolving probe point: identifier 'kernel' at /usr/share/
> source: probe vfs.read = kernel.
> ^
>
> [...]
> Pass 2: analysis failed. [man error::pass2]
> Tip: /usr/share/
>
> It does not appear that an update to a newer systemtap version is going
> to be of any use on 14.04.
> [...]
This message indicates not something wrong with systemtap, but
something wrong with the installation of kernel debugging symbols.
(See also the error::pass2 man page and the given README.Debian file.)
- FChE