Description of problem:
The output of opreport, especially when it comes to symbols in glibc,
uses internal aliases for the symbols in the output.  This is pretty
irritating to somebody who does not know what this means.  The names
can be chosen in a cleverer way to avoid this confusion.

Version-Release number of selected component (if applicable):
oprofile-0.8-20040511.12

How reproducible:
always

Steps to Reproduce:
1.oprof_start, record, and stop
2.opreport --symbols
3.
  
Actual results:
Something like
1         0.0422  0              0  2         0.1063  libc-2.3.3.so  
         __GI_getenv
1         0.0422  0              0  0              0  libc-2.3.3.so  
         __GI_getpid
1         0.0422  0              0  0              0  libc-2.3.3.so  
         __GI_strchr


Expected results:
1         0.0422  0              0  2         0.1063  libc-2.3.3.so  
         getenv
1         0.0422  0              0  0              0  libc-2.3.3.so  
         getpid
1         0.0422  0              0  0              0  libc-2.3.3.so  
         strchr



Additional info:

While correct, the __GI_* names are not the preferred names.  There
are various aliases which are better suited.  In sprof, I'm using the
following code:

          /* The function is already defined.  See whether we have
             a better name here.  */
          if (((*existp)->hidden && !newsym->hidden)
              || ((*existp)->name[0] == '_' && newsym->name[0] != '_')
              || ((*existp)->name[0] != '_' && newsym->name[0] != '_'
                  && ((*existp)->weak && !newsym->weak)))
            *existp = newsym;


I.e., the rules are: if symbol A is already found for a given address
and a second symbol B with the same address is located:

1. if A is hidden and B is not hidden, chose B

2. if first char of A is _ and the first char of B is not _, chose B

3. if both names don't start with _ and A is a weak symbol while B is
   not, chose B

4. stay with A


This all might apply to some other oprofile tools as well.