[yogesh.bit2006]

Hi ,

I was trying to profile xbmc with gprof but gprof generated following error:

gmon.out: No such file or directory when I used following command:

gprof ./xbmc.bin

I am using latest xbmc and I have configured xbmc with "--enable-profiling" option.

I also tried to profile xbcm with valgrind with following command:

valgrind --tool=callgrind ./xbmc.bin

but it generated following error:

==3930== Callgrind, a call-graph generating cache profiler
==3930== Copyright © 2002-2010, and GNU GPL'd, by Josef Weidendorfer et al.
==3930== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==3930== Command: ./xbmc.bin
==3930==
==3930== For interactive control, run 'callgrind_control -h'.
--3930-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a

valgrind: m_debuginfo/readdwarf.c:2391 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
==3930== at 0x3803179F: report_and_quit (m_libcassert.c:209)
==3930== by 0x38031919: vgPlain_assert_fail (m_libcassert.c:283)
==3930== by 0x380B06B8: copy_convert_CfiExpr_tree (readdwarf.c:2391)
==3930== by 0x380B0A24: summarise_context (readdwarf.c:2134)
==3930== by 0x380B257C: run_CF_instructions (readdwarf.c:3654)
==3930== by 0x380B58AC: vgModuleLocal_read_callframe_info_dwarf3 (readdwarf.c:4192)
==3930== by 0xFFFFFFFB:

sched status:
running_tid=1

Thread 1: status = VgTs_Runnable
==3930== at 0x42D9AF93: mmap (in /lib/ld-2.14.1.so)
==3930== by 0x42D8A715: _dl_map_object_from_fd (in /lib/ld-2.14.1.so)
==3930== by 0x42D8BEA3: _dl_map_object (in /lib/ld-2.14.1.so)
==3930== by 0x42D90C37: openaux (in /lib/ld-2.14.1.so)
==3930== by 0x42D92A0E: _dl_catch_error (in /lib/ld-2.14.1.so)
==3930== by 0x42D871EC: dl_main (in /lib/ld-2.14.1.so)
==3930== by 0x42D97F63: _dl_sysdep_start (in /lib/ld-2.14.1.so)
==3930== by 0x42D89010: _dl_start (in /lib/ld-2.14.1.so)
==3930== by 0x42D85256: (in /lib/ld-2.14.1.so)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.


Thanks,
Yogesh