[Systemtap] questions about systemtap

For the latest installation steps, see

Http://blog.csdn.net/zklth/article/details/7281958

In the official tutorial of systemtap, we always recommend that you install the corresponding version of debuginfo package for the kernel during installation. However, for the systemtap installed by centos by default, I can still use some probes normally.

In addition, after I upgrade the kernel on a machine with the debuginfo package installed, systemtap can still be used normally (the debuginfo package is not installed in the upgraded kernel.

 

Updated on February 21,. The above statement is incorrect.

The correct sequence for installing systemtap is to first upgrade the kernel, and then install the debuginfo-common, debuginfo, and kernel-devel packages of the same version number, for example:

Rpm-IVH kernel-2.6.18-194.8.1.el5.x86_64.rpm
Rpm-IVH kernel-debuginfo-common-2.6.18-194.8.1.el5.x86_64.rpm
Rpm-IVH kernel-debuginfo-2.6.18-194.8.1.el5.x86_64.rpm
Rpm-IVH kernel-devel-2.6.18-194.8.1.el5.x86_64.rpmOnly after the package is installed/Usr/src/kernels/2.6.18-194.8.1.el5-x86_64
Rpm-IVH kernel-headers-2.6.18-194.8.1.el5.x86_64.rpm

Otherwise, the error "missing x86_64 kernel/module debuginfo under '/lib/modules/'uname-R'/build'" will occur during script execution.'/Lib/modules/'uname-R'/build '"Is a link pointing to the kernel source code directory/Usr/src/kernels/'uname
-R',.

when I upgrade the kernel to Linux 2.6.34.7, The systemtap script can be correctly executed without installing the kernel-devel of the corresponding version, this is because the source code directory contains the relevant modules required for systemtap execution.