While debugging in an MFS, I can look at the stack and determine what subroutine/event made the FS call - is there anyway to access the data in the stack from within the MFS itself? The goal is to capture what event/subroutine is making a specific change to a specific file in hopes of finding a bug that is wiping out data.
Sean,
Yes, Take a look at the results of the RetStack() function. It will show you the entire call stack as is shown in the debugger.
Hope this helps,
Yes, that works, thank you!