Scott Martin wrote:
> My environment is:
> SUSE Enterprise Server 10 (ppc), Version 10. Patch 2
> cat /proc/version shows: Linux version 188.8.131.52-0.21-ppc64
> (geeko@...) (gcc version 4.1.2 20070115 (SUSE Linux))
> I setup as follows:
> 0. installed rpms popt-devel-64bit-1.7-271.27 and popt-devel-1.7-271.27 (due
> to an error message running /configure otherwise)
> 1. I installed oprofile .94 from sourceforge using ./configure
> 2. I initialized via opcontrol --setup --vmlinux=/boot/vmlinux-`uname -r`
> When I run opreport --symbols --image-path=/lib/modules/`uname -r`, or just
> oreport --symbols, I get the following error:
> warning: [heap] (tgid:31527 range:0x10015000-0x10036000) could not be found.
> /lib/modules/184.108.40.206-0.21-ppc64/kernel/security/apparmor/apparmor.ko is
> not in a usable binary format.
> warning: /bin/bash is not in a usable binary format.
> ./run_oprofile.sh: line 25: 31628 Segmentation fault opreport --symbols
> --image-path=/lib/modules/`uname -r`
The "not in a usable binary format" message may be due to some BFD mixup --
i.e., the version of the library being dynamically linked with at runtime
doesn't match the version used at build time. Additionally, I've seen seg
faults with the same underlying cause. Please run opreport with gdb to see if
it's seg faulting on a bfd library call. If so, closely examine your build and
runtime BFD environments to make sure they match.
> I need the output with symbols. I appreciate any help resolving this.
> Thank you.