Hi,
I am just trying to use the profiling tools, used Yocto & buildroot buildsystem to crosscompile the oprofile by enabling the kernel profiling tokens. Previously 1.1.0 version was working good. But the new version 1.3.0 fails as below. Could you help me to debug this further?
root@beaglebone-yocto:~# operf -version
Unexpected error running operf: Operation not supported
It doesn't look like "Operation not support" is coming from operf. The message doesn't seem to be in the oprofile source code. could you do a "which operf" to check to see which operf is being run? Could you give more destails on how oprofile-1.3.0 was built and installed on the machine? Where is oprofile installed on the machine? You might try to use the full path to make sure that the desired one is being used. Is it possible run "strace operf --version" to get a better idea when and where things go wrong?
If you go back to installing oprofile-1.1.0 everything works fine?
Hi William,
Yes I too grep from the same and found none, but I could see the profiling works good when the version was downgraded to 1.1.0.
Just added the profiling tools and oprofile from meta-Openembedded in yocto & selected oprofile from Buildroot. Found the same issue.
Here is the log;
Hi,
I too grep for the same and didn't get any way to trace this.
I just build the package from Yocto (meta-openembedded) and buildroot both, which yields the same.
Yes with the same build system for 1.1.0 was working good.
Find the attached strace log and which operf
What does the strace output look like for the oprofile-1.1.0 operf?
Does the oprofile-1.1.0 build have any patches in it? Or is it the completely stock oprofile-1.1.0?