Steve Loft wrote:
Thanks, Frank. So far I haven't been able to discover much from using FrameAddress, but from experimenting a bit it does seem to point to a stack problem.
What are the figures? How many bytes of stack are used in each level? Is it more than you expected? Does the total bytes used actually exceed the resource limit? (Otherwise the problem might be something else after all, like an "ordinary" out of range access.)
Could the fact that recursive_two is inside recursive_one be causing problems when recursive_one calls itself?
Not by itself. Of course, indirect recursive calls means more active frames on the stack, but if they're all small, the sum should still be small.
Frank