MAP specific issues
This section includes details about known issues with Arm® MAP.
MPI wrapper libraries
Thread support limitations
Solution
No thread activity while blocking on an MPI call
Solution
I am not getting enough samples
Solution
I just see main (external code) and nothing else
Solution
Arm® MAP reports time spent in a function definition
Arm® MAP does not correctly identify vectorized instructions
Linking with the static Arm® MAP sampler library fails with FDE overlap errors
Solution
Linking with the static Arm® MAP sampler library fails with an undefined references to “__real_dlopen”
Solution
Arm® MAP adds unexpected overhead to my program
Arm® MAP takes an extremely long time to gather and analyze my OpenBLAS-linked application
Solution
Arm® MAP over-reports MPI, Input/Output, accelerator or synchronization time
Solution
Arm® MAP collects very deep stack traces with boost::coroutine