I'm trying to profile the asm code of xvidcore. As it's
written in nasm language, i knew i could not get debug info,
so i used yasm, a nasm compatible assembler which supports
stabs debug output.
Debug information is really present in the object/so files,
but opannotate -s only profiles the first symbol of each asm
file. I tried to contact yasm authors, but their ML, and the
main author seems to be non reachable, that's why i'm asking
here what could be wrong.
Reading through your ML, i discovered we weren't defining
symbols as functions, but now this is fixed. And i'm even
defining symbols' size. Now a readelf output is closer to what
i use to have with gcc compiled objects.
In a last attempt i'm using preprocessed files... but no luck.
Using these files with gdb or insight allows me debugging
correctly the bins, so the stab info seems to be right. What
am i doing wrong ?
I can provide patches against xvidcore cvs in order to help
you working with preprocessed files+symbols' size if that
really matters (i was hetting the same results anyway)
PS: i'm using oprofile utilities from today's cvs, with an
oprofile module from 22.214.171.124.
 http://www.tortall.net/projects/yasm/ use nightly
 This opannotate+opreport file shows the problem
see sad16_3dne, sad8_3dne, both are used (flat profile
proves it), but only the first function is instrumented
Edouard Gomez (ed.gomez@...) wrote:
> Debug information is really present in the object/so files,
> but opannotate -s only profiles the first symbol of each asm
Not that i'm in a hurry, but is there anyone looking at this
issue or may i simply unsubscribe this ML and go on
workarounding this one way or another ?
I'm really looking for advice, is that a bug in oprofile,
yasm, my testing ?