Pointer-P overflow depth limit exceeded 30

I am profiling code with Scalasca 2.0

that uses some recursion.

When I run the parser with scalasca -analyze myexec

, it doesn't throw any errors until the end where it says:

Score-P callpath depth limitation of 30 exceeded.
Reached callpath depth was 34

      

At this point the scalasca results are corrupted and I am unable to run cube

on the released output files.

I know for sure that the number of self-twisting for repeated calls will not be more than 34.

I read that there is a variable that takes into account the number of "measured call paths" (see https://www.dkrz.de/Nutzerportal-en/doku/blizzard/program-analysis/profiling ). So, I also tried to run scalasca with export ESD_FRAMES=40

, but scalasca still says the limit is 30

.

So, is there a way to move this scalasca limit to a higher value?

+3


source to share


1 answer


I am writing my answer 2 months after you posted the question, so most likely you have already found a solution.

In rating-p 1.4+ it can be fixed with



export SCOREP_PROFILING_MAX_CALLPATH_DEPTH=128 

      

+2


source







All Articles