On Dec 12, 2011, at 11:04, Robert Ngan wrote: > All I want to do at this point is determine where the mismatching BAKR/PR > occurs. We can't "see" which is the active stack entry, but can at least > compare the the contents of the stacked registers in the current entry > before/after a suspect call and assume there's a mismatch if they're > different. > The empty stack condition is a non-issue as it turned out the invoking > program using BAKR/PR so if we encounter an empty stack condition it is > also a mismatch. > The empty stack test may not be definitive if there are several prior entries on the stack and some of them remain.
What's really needed is the ability to save the stack depth at the beginning of a code segment and compare it after. -- gil
