Community
Participate
Working Groups
The current behaviour of Eclipse Oprofile is to load the oprofile module if not loaded, set up opcontrol, and run opcontrol. The binary is run exactly once, followed by collecting any profiling information with opreport. Since Oprofile is a statistical profiler, multiple runs of a binary would benefit in collecting more samples (especially in the case of binaries that produce few or no samples). This could be an option in the Oprofile configuration of a project. The only change in behaviour would be that the binary being profiled could be run multiple times, before data is collected.
This is a fine idea.
This has been reviewed here https://git.eclipse.org/r/#/c/10204/ and is in master. Marking this bug as closed (fixed). Thanks to Rafael for doing this.