1 of 1 people found this helpful
CodeAnalyst currently uses a low-overhead, statistical approach for profiling. If all your functions ran for a similar amount of time, the timer-based profile would give you coverage. However, since it is possible to never sample an infrequently called or small function, I would recommend against using it for coverage results.
It sounds like you want an instrumented approach, which could track all basic blocks executed. This is very intrusive with high overhead and not representative of the optimized performance your code is capable of.
We will add your use case as an enhancement request. Thanks!
It ssems that I had wrong assumpitions of how profiling works.
Thank you for the calrification and the quick answer.
However, it would still be nice to know which code was executed and so I am hoping that the enchancement request will someday be implemented ;)
Since the coverage file's format is not documented by ESRI, this document is mainly based on the analysis of binary dumps of the files.