Re: Code Profiling Function ID
Stole an I/O, toggles on entry and ext. Placed another I/O change in the same location on all the major routines. Change the I/O (to the scoped output) in the routine, measure the time, compare to the usage window, dang... it works but what a work around. Each I/O R/W time is constant so swapping them doesn't effect the timing, just which signal is being looked at.
The routine address changes each iteration so even when you ID it, chasing it... Heisenberg here we come. If anyone has something better for the future, I'm all ears.