<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi,<br>Have you installed debug symbols of all your dependent packages ? Use debug-dep-install script on maemo-debug-scripts package.<br><br>For Oprofile to work more accurately, we need to collect as many samples as possible. Running the scenario for some more duration may help.<br><br>Also, have you tried the "separate" options ? <br><br>> One more question: how can I see the total time taken by a function? I would<br>> expect to see the main() function of Mapper at the top of the list, as it's<br><br>Yes, Valgrind(Callgrind tool) helps. But, it may not help here as its only for x86 environment.<br><br>Regards,<br>Chitti<br><br>On Sun, Apr 11, 2010 at 10:46 AM, Alberto Mardegan<br><mardy@users.sourceforge.net> wrote:<br>> ?again I've tried to profile Mapper on the N900, with no results. First I<br>> tried gprof, but it gives me all 0.0 times
(and a google search reveals that<br>> this is a common problem in maemo, even though I didn't find an explanation<br>> of it); then I tried oprofile, which gives me an output like this:<br>><br>> ==========<br>> samples ?% ? ? ? ?image name ? ? ? ? ? ? ? symbol name<br>> 3007 ? ? 38.3497 ?no-vmlinux ? ? ? ? ? ? ? /no-vmlinux<br>> 1083 ? ? 13.8120 ?libclutter-eglx-1.0.so.0.8.0<br>> /usr/lib/libclutter-eglx-1.0.so.0.8.0<br>> 424 ? ? ? 5.4075 ?libc-2.5.so ? ? ? ? ? ? ?memcpy<br>> 336 ? ? ? 4.2852 ?libpng12.so.0.37.0 ? ? ? png_do_expand_palette<br>> 317 ? ? ? 4.0429 ?libz.so.1.2.3 ? ? ? ? ? ?/usr/lib/libz.so.1.2.3<br>> 286 ? ? ? 3.6475 ?libGLESv2.so ? ? ? ? ? ? /usr/lib/libGLESv2.so<br>> 219 ? ? ? 2.7930 ?ld-2.5.so ? ? ? ? ? ? ? ?do_lookup_x<br>> 120 ? ? ? 1.5304 ?libglslcompiler.so ? ? ? /usr/lib/libglslcompiler.so<br>> 55 ? ? ? ?0.7014 ?libc-2.5.so ? ? ? ? ? ? ?_int_malloc<br>> 48 ? ? ? ?0.6122
?libpthread-2.5.so ? ? ? ?pthread_mutex_lock<br>> 44 ? ? ? ?0.5612 ?libpixman-1.so.0.15.3 ? ?fbCompositeSolidMask_nx8x8888neon<br>> 36 ? ? ? ?0.4591 ?libsrv_um.so ? ? ? ? ? ? /usr/lib/libsrv_um.so<br>> 35 ? ? ? ?0.4464 ?libc-2.5.so ? ? ? ? ? ? ?malloc<br>> 35 ? ? ? ?0.4464 ?libsqlite3.so.0.8.6 ? ? ?/usr/lib/libsqlite3.so.0.8.6<br>> 34 ? ? ? ?0.4336 ?libc-2.5.so ? ? ? ? ? ? ?memset<br>> 34 ? ? ? ?0.4336 ?libglib-2.0.so.0.2000.3 ?g_slice_alloc<br>> 32 ? ? ? ?0.4081 ?libglib-2.0.so.0.2000.3 ?g_hash_table_lookup<br>> [...]<br>> ==========<br>> (I got this output after moving the oprofile collected data into Scratchbox)<br>><br>> But this doesn't help me, as Mapper's own functions appear on the bottom of<br>> the list and seem to take very little time. I tried to use the "-c" option<br>> of opreport to see the call graph, but it doesn't seem to be working<br>> properly, as for every function it gives this
output:<br>><br>> ==========<br>> -------------------------------------------------------------------------------<br>> 336 ? ? ? 4.2852 ?libpng12.so.0.37.0 ? ? ? png_do_expand_palette<br>> ?336 ? ? ?100.000 ?libpng12.so.0.37.0 ? ? ? png_do_expand_palette [self]<br>> -------------------------------------------------------------------------------<br>> ==========<br>><br>> It seems it cannot resolve the caller, why?<br><br>Did you try to reinitialize OProfile?<br><br>> One more question: how can I see the total time taken by a function? I would<br>> expect to see the main() function of Mapper at the top of the list, as it's<br>> clearly the function that takes most time, but it doesn't even appear in the<br>> list at all.<br>> So I assume that these times are net (that is, the time spend in subroutines<br>> is excluded from the function times), which might be useful in some case,<br>> but it definitely
prevents me from knowing what functions in Mapper need to<br>> be optimized...<br><br>I use Gprof2Dot for that:<br>http://wiki.jrfonseca.googlecode.com/hg/gprof2dot.png<br><br>I just added some basic information for this here:<br>http://elinux.org/OProfile<br><br>Cheers.<br><br>-- <br>Felipe Contreras<br></td></tr></table><br>