Stack sampling on device

I'm running some C code on the device and trying to figure out what I can do to make it faster. Unfortunately, I'm having trouble figuring out how to get the information I need from the tools available.

In this case, 99.7% of the time spent is in "hidden (pdpathfinder.c:568". Is this part of the API? Is there a way to tell where I'm calling this code from? Something like stack sampling would be really nice or, failing that, some of the source for the internal libraries would really help with debugging / profiling.

1 Like

The Simulator has a Sampler window, which can be set to measure Device instead of itself. The reported functions have disclosure triangles you can click to drill down, with code line numbers. Is that what you need?

1 Like

Thanks @AdamsImmersive. I was using that feature and that’s how I got this information.

It seems that I’m stuck in some API code?

I’d hoped to be able to get a stack sample so I can see where things are being called from.