I'm running the call stack analysis and i've found that a function in a dll is responsible for a lot of the used time. However, I can't see the call stack analysis across the dll boundary.
Is it possible to view this information, or does the call stack analysis simply stop at dll boundaries when sampling?
I also would like to know how to get data that crosses DLL boundaries. I'm using the call stack sampling and the ancestors seem to be cut off as soon as the call crosses the boundary of the DLL. It' s very annoying since the software I'm profiling is heavily DLL-based.