Incorrect results when profiling cmsRun
Running the profiler on cmsRun turns up a failure. For an input file that takes cmsRun about 5 minutes to process, the profiler only gets about 250 samples (slightly different number of samples each time). I do not understand the source of the problem. The total number of samples should be around 30,000 for a 5-mintue program run.
It appears that cmsRun may be masking the SIGPROF signal. Somehow, igprof is able to work with cmsRun.
- Status changed from New to Resolved
- Estimated time set to 16.00 h
Had to add a pthread_sigmask override function to the preload library. This is the strick that igprof uses. It intercepts cmsRun's blocking of SIGPROF and does not allow it.
- % Done changed from 0 to 100
- Estimated time deleted (
- Status changed from Resolved to Closed
Also available in: Atom