Red Hat Bugzilla – Bug 622867
Profiling of binaries does not work if Eclipse project is NOT in Eclipse workspace
Last modified: 2011-05-19 07:43:37 EDT
Created attachment 437927 [details]
Patch: Fix for this problem
Description of problem:
Profiling of binaries does not work if Eclipse project is NOT in Eclipse workspace. Profiling works fine if project is inside workspace.
Version-Release number of selected component (if applicable): 0.5.0
How reproducible: Always
Steps to Reproduce:
1. Create new project
2. Uncheck "Use default location"
3. Compile, try to profile binary
4. Eclipse shows "No profiling data is on the system" because wrong path to binary is used.
When looking at /root/.oprofile/daemonrc
$ grep IMAGE_FILTER /root/.oprofile/daemonrc
But since it's an external project this path does not exist.
No profiling data is on the system
Results of profiling.
Additional info: Upstream bug-report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=321905
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
eclipse-oprofile-0.6.1-1.el6 has been built.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.