I think is this mostly a question for Mike, but I'll send it more broadly.
Looking at the C API it looks like the two alternatives for providing access to the image of the code that was traced is either through in-memory buffers or as binary files. I currently don't see a way to remove the accessors should the memory locations be "invalidated".
Would it be possible to add the ability to remove accessors and also to add a third type of accessor, a pointer to a function that will access the requisite locations when called?
--- Tor Jeremiassen, Ph.D. Senior Member Technical Staff SDO Foundational Tools Texas Instruments Ph: 832 939 2356 13905 University Lane Fax: 832 939 2015 Sugar Land, TX 77479 Email: tor@ti.com