Systemtap - Red Hat ENTERPRISE LINUX 5.4 - TECHNICAL NOTES Manual

semanage fcontext -a -t textrel_shlib_t '/usr/lib/ooo-1.1(/.*)?'
semanage fcontext -a -t textrel_shlib_t '/usr/lib64/ooo-1.1(/.*)?'
restorecon -Rv /usr/lib/ooo-1.19
restorecon -Rv /usr/lib64/ooo-1.19
Alternatively, you can also upgrade your OpenOffice to a correct version compatible with SELinux
in Red Hat Enterprise Linux 5. You can do this by subscribing to the "Productivity App" child channel
in Red Hat Network and running the following command:
yum install openoffice-
{base,calc,draw,emailmerge,graphicfilter,headless,impress,javafilter,math,pyuno,wri
104
(BZ#477103)

4.30. systemtap

SystemTap provides an instrumentation infrastructure for systems running the Linux 2.6 kernel. It
allows users to write scripts that probe and trace system events for monitoring and profiling purposes.
SystemTap's framework allows users to investigate and monitor a wide variety of wide variety of kernel
functions, system calls, and other evens that occur in both kernel-space and user-space.
The following are the Known Issues that apply to the systemtap package in Red Hat Enterprise Linux
5.4
• Running some user-space probe test cases provided by the systemtap-testsuite package fail
with an Unknown symbol in module error on some architectures. These test cases include (but
are not limited to):
• systemtap.base/uprobes.exp
• systemtap.base/bz10078.exp
• systemtap.base/bz6850.exp
• systemtap.base/bz5274.exp
Because of a known bug in the latest SystemTap update, new SystemTap installations do not
unload old versions of the uprobes.ko module. Some updated user-space probe tests provided by
the systemtap-testsuite package use symbols available only in the latest uprobes.ko module (also
provided by the latest SystemTap update). As such, running these user-space probe tests result in
the error mentioned earlier.
If you encounter this error, simply run rmmod uprobes to manually remove the older uprobes.ko
module before running the user-space probe test
• SystemTap currently uses GCC to probe user-space events. GCC is, however, unable to provide
debuggers with precise location list information for parameters. In some cases, GCC also fails to
provide visibility on some parameters. As a consequence, SystemTap scripts that probe user-space
may return inaccurate readings.
again.(BZ#499677)
106
(BZ#239065)
systemtap
105
311