[ oprofile-Bugs-1249755 ] PPC/E500 no symbols

[SourceForge.net <no...@so...>]

Bugs item #1249755, was opened at 2005-08-01 11:34
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116191&aid=1249755&group_id=16191

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: PPC/E500 no symbols

Initial Comment:
On a PPC/E500 system with kernel oprofile support, I 
can't get any symbol information with opreport or 
opannotate even when the kernel and user-space 
binaries of interest have been compiled with "-g". Tried 
oprofile 0.9.1.

Compiled oprofile like this:
# ./configure --with-kernel-support
# make
# make install

Started oprofile like this:
# opcontrol --reset
# opcontrol --vmlinux=/boot/vmlinux.op
# opcontrol --start
# Ran the GNU hello program in a loop
# opcontrol --stop
# opreport --symbols
CPU: e500, speed 0 MHz (estimated)
Counted CPU_CLK events (Cycles) with a unit mask of 
0x00 (No unit mask) Count 100000
Samples %      image name   app name    symbol name
282720  96.8870 vmlinux.op  vmlinux.op    (no symbols)
3813       1.3067  oprofiled    oprofiled      (no symbols)
1708       0.5853  bash          bash            (no symbols)
660         0.2262  vmlinux.op  hello            (no symbols)
...
5            0.0017   hello           hello           (no symbols)
...


# opannotate -a -x hello
/* 
 * Command line: opannotate -a -x hello 
 * 
 * Interpretation of command line:
 * Output annotated assembly listing with samples
 * 
 * CPU: e500, speed 0 MHz (estimated)
 * Counted CPU_CLK events (Cycles) with a unit mask 
of 0x00 (No unit mask) count 100000
 */
               :
               :/home/aprem/hello-2.1.1/src/hello:     file 
format elf32-powerpc
               :
               :Disassembly of section .init:
               :Disassembly of section .text:
               :Disassembly of section .fini:
               :Disassembly of section .got:


However,

# objdump -S -l -d hello
...
...
100008cc <main>:
main():
/home/aprem/hello-2.1.1/src/hello.c:116
int
main (argc, argv)
     int argc;
     char *argv[];
{
100008cc:       94 21 ff 60     stwu    r1,-160(r1)
100008d0:       7c 08 02 a6     mflr    r0
100008d4:       90 01 00 a4     stw     r0,164(r1)
/home/aprem/hello-2.1.1/src/hello.c:120
  int optc;

...
...


Any info on how to get symbol information on 
PPC/E500 would be appreciated.

Thanks,

Ajit
Aji...@mo...




----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-08-02 12:11

Message:
Logged In: NO 

I don't have a ppc 32 machine to try thing out on, but I do
have a couple suggestions in identifying the cause of the
problem.

Verify that the debugging informatoin generated by the
compiler is usable. Try using gdb on the program. It is
possible that there is some problem in the debugging
information generated by the compiler.

Is there a version of OProfile that did work on the
ppc/e500? If there is a version that is known to work on
ppc/e500, one of the common techniques used to narrow down
the problems with gcc could be used, a binary search. Check
out a version halfway between the working and non-working
versions. Figure out which half of the version range the
problem change occured in. Repeat until down a single change
set is the difference between the problem occuring and not
occuring.

-Will

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-08-01 11:44

Message:
Logged In: NO 

Do any of the older versions of oprofile, e.g. 0.8, work 
and map the information back to functions? Some changes were
made in April this year for the ppc64 to handle synthetic
symbol and I am wondering if those have any effect on this
not working on ppc/e500.

-Will

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116191&aid=1249755&group_id=16191