Re: Is oprofile still working?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Peter Kjellstrom wrote:
> I guess that means that there is a problem with the data collected. 
> All the
> warnings about vdso ranges that can't be found is strange (I don't get that 
> here). Are the tgids in that list special in any way?
>   
I'm not sure what would make tgids special - as I'm not exactly sure 
what they are in the first place (some sort of special thread id's?).
> Is this on a single machine or on several?
>   
Seems to be happening on two separate machines - both 32bit, though.
> Do you know if this strange behaviour persists over reboots?
>   
Yes, a reboot doesn't seem to make any difference.
> Anything strange in ~/.oprofile? If you don't have customizations remove it 
> and let oprofile re-create it.
>   
I've tried that now - again, doesn't seem to make any difference.

I also uninstalled oprofile, did a "rm -r /var/lib/oprofile", and a 
reinstall, but I still get the same behaviour.

> I notice that you're on 32-bit while I'm on x86_64. That may or may 
> not be
> relevant. I don't have any 32-bit machines around to test on though. 
>
>   
Maybe this is the problem then.

What we need is someone else to report that oprofile works on a 32-bit 
machine to confirm that I'm totally jinxed :-)

Hywel.

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux