Re: Problem with symbol info. Binutils?

[Philippe E. <ph...@wa...>]

Guillermo Ballester Valor wrote:
> Hi,
> 
> I'm new in this list, and I'm impressed with Oprofile, is the kind of profiler 
> I've been searching for a long while. Thanks to the devloper team :-)
> 
> Well, I've installed oprofile-0.5.3 in two SuSE 8.0 boxes, one is a PentiumIII 
> and the other is a Pentium4. I had to use my own kernel (not SuSE kernel) 
> because of a segfault when loading modules (I also see this problem in the 
> list). Reusing SuSE 8.0 kernel config file, doing a 'make oldconfig' and 
> building a new 2.4.21-rc6 and _ALL_ runs OK.  Good!.
> 
> But the problems began with a SuSE 8.2 (Athlon XP) box. I made the same, and 
> oprofile runs but I'm not able to see any symbolic info. I.e, compiling a 
> binary with -g options, being able to see all sort of debug and symbolic info 
> with objdump, readelf, nm ... op_to_source and oprofpp cannot show any 
> detailed info.

is $ oprofpp -L /your/application -t vsnl
shows debug line information like this ? :


0804e5bc 10 op_get_line 
/usr/src/phe/sf/oprofile-0.5.3/libutil/op_fileio.c:227
0804ad64 12 opd_find_image 
/usr/src/phe/sf/oprofile-0.5.3/dae/opd_image.c:265


if yes check than the source are available in this path

> 
> As example, this is the output of a session (gprof gives all information 
> right)

if you don't get any source line information from oprofpp, is
gprof -a able to show the source ?

> 
> /*
>  * Command line: op_to_source -s Glucas

...

>                :Desensamblado de la sección .fini:
> -----------------------
> 
> It seems like oprofile cannot read symbolic info. Is it an oprofile problem or 
> a binutils problem? Or perhaps is mine?.

dunno now,

regards,
Phil