On 05/11/12 08:45, DJ Delorie wrote: > That's what we're trying to do, but the CFA corresponds to the > "normal" cfa but with a different (wrong) return address. The > fallback handler corrects the RA and the next iteration sees the > corrected frame.
I think some ascii art or a pointer to a manual may be required here. I'm a bit confused as to how the fallback handler can find the correct RA but the "normal" unwind path can't. How do all these things fit on the stack? r~
