On Apr 29, 2011, at 9:12 AM, Silvius Rus wrote: > When you build with > -fprofile-generate=./fdoprof, the output gets dumped under > ./fdoprof/..., but there seems to be no easy way to know this path > within the profiling process. For Google servers this makes > collection fragile. The user generally does not have access to the > server file system. I implemented a collection mechanism so the user > can tell the server "copy the profiles from ./fdoprof to some shared > location". But now you need to pass the exact path when building > *and* collecting profiles, which may get separated in time, thus the > process is fragile. It would be good to keep a copy of the path > prefix and have it accessible through a public interface as well. > Then once an instrumented binary is built, it will know the root of > the profile output directory and thus relieve the user from the > responsibility of knowing it.
So, does GCOV_PREFIX_STRIP and GCOV_PREFIX help you obtain more certainty and reliability?
