From: Maynard J. <may...@us...> - 2012-02-22 22:20:02
|
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "oprofile". The branch, master has been updated via ab45a0cc5d1cf522c1aef8f22ed512a9aae0dc1c (commit) from 2b100b4459572bc313d8850ebdda6639a9c6a595 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit ab45a0cc5d1cf522c1aef8f22ed512a9aae0dc1c Author: Maynard Johnson <may...@us...> Date: Wed Feb 22 16:08:12 2012 -0600 Symptom: If runtime binaries have been stripped of symbol information, users must make debuginfo files available that contain the symbol information for those bianries so that opreport can attribute samples to symbols for those binaries. But in a prelinked environment (e.g., RHEL, Fedora), opreport does not correctly process the debuginfo files, thus generating report data such as the following: samples % image name symbol name 1531 6.2205 libcairo.so.2.11000.2 /usr/lib64/libcairo.so.2.11000.2 In the example given above, the debuginfo package corresponding to the cairo package has been installed. Note that this problem only occurs where the runtime binary is completely stripped of symbol information. So on RHEL and Fedora, basic symbol information is retained in the runtime libc library, so this symptom does not appear with samples taken in libc. This patch reverts previous changes that actually broke this functionality. The changes being reverted are: - The SEC_LOAD filter - Calling translate_debuginfo_syms for all architectures ----------------------------------------------------------------------- Summary of changes: libutil++/bfd_support.cpp | 23 +++++++---------------- libutil++/bfd_support.h | 15 +++++++-------- 2 files changed, 14 insertions(+), 24 deletions(-) hooks/post-receive -- oprofile |