error::buildid(7stap) [centos man page]
ERROR::BUILDID(7stap) ERROR::BUILDID(7stap) NAME
error::buildid - build-id verification failures DESCRIPTION
Because systemtap's script translation / execution stages may be executed at different times and places, it is sometimes necessary to ver- ify certain invariants. One such invariant is that if a script was informed by translate-time analysis of executables, then those same executables need to be used at run time. This checking is done based upon the build-id, a binary hash that modern (post-2007) compil- ers/toolchains add as an NT_GNU_BUILD_ID ELF note to object files and executables. Use the readelf -n command to examine the build-ids of binaries, if you are interested. Only scripts are sensitive to executables' build-ids: generally those that perform deep analysis of the binaries or their debuginfo. For example, scripts that place .function or .statement probes, or use stack backtrace-related tapset functions may be sensitive. Other scripts that rely only on process.mark or kernel.trace probes do not require debuginfo. See the DWARF DEBUGINFO section in the stap- probes(3stap) man page. During translation, systemtap saves a copy of the relevant files' build-ids within the compiled modules. At run-time, the modules compare the saved ones to the actual run-time build-ids in memory. The error message indicates that they did not match, so the module will decline placing a probe that was computed based upon obsolete data. This is important for safety, as placing them at an inappropriate address could crash the programs. However, this is not necessarily a fatal error, since probes unrelated to the mismatching binaries may operate. A build-id mismatch could be caused by a few different situations. The main one is where the executable versions or architecture were dif- ferent between the systemtap translation and execution times/places. For example, one may run a stap-server on a slightly different ver- sion of the OS distribution. The kernel running on the workstation may be slightly different from the version being targeted - perhaps due to a pending kernel upgrade leaving different files on disk versus running in memory. If your OS distribution uses separate debuginfo packages, the split .IR .debug files may not exactly match the main binaries. SEE ALSO
http://fedoraproject.org/wiki/Releases/FeatureBuildId, stap(1), stapprobes(3stap), warning::debuginfo(7stap), error::reporting(7stap) ERROR::BUILDID(7stap)
Check Out this Related Man Page
STAP(7) Miscellaneous Information Manual STAP(7) NAME
stappaths - systemtap miscellaneous and paths DESCRIPTION
This manual page was generated on 2013-05-14 for systemtap 1.7. The following section will list the main paths in systemtap that are important to know and may be required to reference. Tapset Path: /usr/share/systemtap/tapset/ Systemtap data directory for cached systemtap files, unless overridden by the SYSTEMTAP_TAPSET environment variable or the XDG_DATA_DIRS environment variable. This directory stores a set of builtin functions and probe point aliases are provided by the scripts installed here. These are described in the stapfuncs(3stap) and stapprobes(3stap) manual pages. Runtime Path: /usr/share/systemtap/runtime/ The runtime sources, unless overridden by the SYSTEMTAP_RUNTIME environment variable. Staprun Path: /usr/bin/staprun The auxiliary program supervising module loading, interaction, and unloading. Stapio Path: /usr/lib/systemtap/stapio The Systemtap module input and output handler. sdt.h Path: /usr/include/sys/sdt.h Kernel debuginfo Path: /usr/lib/debug/lib/modules/$(uname -r)/ The location of kernel debugging information when packaged into the kernel-debuginfo RPM, unless overridden by the SYSTEMTAP_DEBUG- INFO_PATH environment variable. The default value for this variable is +:.debug:/usr/lib/debug:build and can be changed using $env SYSTEMTAP_DEBUGINFO_PATH=/path/to/vmlinux . Elfutils searches vmlinux in this path and it interprets the path as a base directory of which various subdirectories will be searched for finding modules. By default, systemtap will also look for vmlinux in these locations: /boot/vmlinux-`uname -r` /lib/modules/`uname -r`/vmlinux /lib/modules/`uname -r`/vmlinux.debug /lib/modules/`uname -r`/build/vmlinux /lib/modules/`uname -r`/.debug/vmlinux.debug /usr/lib/debug/lib/modules/`uname -r`/vmlinux.debug /var/cache/abrt-di/usr/debug/lib/modules/`uname -r`/ /var/cache/abrt-di/usr/lib/debug/lib/modules/`uname -r`/vmlinux.debug Debuginfo for user-space applications have source files located in /usr/src/debug/ Further file information on user-space applica- tions can be determined per-basis using rpm -ql <package>-debuginfo. For supported user-space applications information please visit the systemtap wiki. $HOME/.systemtap Systemtap data directory for cached systemtap files, unless overridden by the SYSTEMTAP_DIR environment variable. /tmp/stapXXXXXX Temporary directory for systemtap files, including translated C code and kernel object. /lib/modules/VERSION/build The location of kernel module building infrastructure. /usr/share/doc/systemtap*/examples Examples with greater detail, can be found here. Each example comes with a .txt or .meta file explaining what the example, sample or demo does and how it is ordinarily run. $SYSTEMTAP_DIR/ssl/server User's server-side SSL certificate database. If SYSTEMTAP_DIR is not set, the default is $HOME/.systemtap. $SYSTEMTAP_DIR/ssl/client User's private client-side SSL certificate database. If SYSTEMTAP_DIR is not set, the default is $HOME/.systemtap. /etc/systemtap/ssl/client Global client-side SSL certificate database. /etc/systemtap/staprun/ staprun's trusted signer certificate database. /etc/sysconfig/stap-server/ stap-server service global configuration file. /etc/stap-server/conf.d/*.conf stap-server service configuration files for default servers. /var/run/stap-server/ stap-server service default location of status files for running servers. /var/log/stap-server/log stap-server service default log file. FILES
/usr/share/systemtap/tapset SEE ALSO
stapprobes(3stap), stapfuncs(3stap), staprun(8), stapvars(3stap), stapex(3stap), stap-server(8), awk(1), gdb(1) BUGS
Use the Bugzilla link of the project web page or our mailing list. http://sourceware.org/systemtap/,<systemtap@sourceware.org>. Systemtap Team STAP(7)