I am looking for an effective way to analyze an existing model with its complex method structure. My goal is to understand the process, which one MU takes from the "Source" to the "Drain" and to visualize how the established method structure works.
Is there a way to analyze sequentially all methods which are started because of one ( maybe the first) MU ?
Thanks in advance!
Solved! Go to Solution.
well, you can set a condition for the breakpoint e.g.
if condition =true
This would of course mean to touch every method ( either manually or through code)
to implement the debug condition.
It's quicker to press F5 to skip the code until next breakpoint
Maybe using the Profiler can also help you; there you can see which methods called which other methods (and how often), e.g. like this:
When you look at the last 3 rows, you see that M3 was called 10x by M1 and 15x by M2 (in total 25x). The first 4 rows show that the SingleProc.EntranceCtrl has called 60x M1, which in turn has then called M3 10x and M2 30x (and then M2 has called M3 15x).
Not sure whether you can use it for your analysis, though