On Thursday 12 August 2010, Hywel Richards wrote: > Hi all, > > Is anyone using oprofile? > > I'm getting segfaults from opreport at the moment, and I'm not sure if > it is opreport, or just me. I've tried the steps you outline below and it works for me (updated C5.5 as of 10m ago). My only guess is that your binary is b0rked. What happens if you do "opreport -l" instead of "opreport -l /tmp/myprog"? Was myprog compiled with "-g"? And just to be sure, could you provide "uname -a" and "rpm -q oprofile". /Peter > In case it is something just plain daft I am doing, here is how it goes: > > opcontrol --reset > opcontrol --setup --no-vmlinux > opcontrol --start > > ... now I run my program, /tmp/myprog ... > > opcontrol --dump > opcontrol --shutdown > > then I run, > opreport -l /tmp/myprog > and get: > warning: [vdso] (tgid:4780 range:0x8d7000-0x8d8000) could not be found. > warning: [vdso] (tgid:4784 range:0x860000-0x861000) could not be found. > CPU: Core Solo / Duo, speed 1067 MHz (estimated) > Counted CPU_CLK_UNHALTED events (Unhalted clock cycles) with a unit > mask of 0x00 (Unhalted core cycles) count 100000 > Segmentation fault ...
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
