In case anyone wonders why I don’t like LDRA a whole lot (it’s good, it saves a lot of time, but it could be a lot easier to use) this is one good example. Poor Karl ran into this extremely “helpful” error message:

127

So I figured out what that error message means. Apparently the code generated by LDRA was incorrect. The function was trying to return a reference to a local variable. Not good. (For those of you who aren’t programmers, a local variable only exists inside the function it was declared in so if you return a reference to it then whoever called that function tries to use that reference except the local variable doesn’t exist anymore).

I’m just impressed that program didn’t crash.

If anyone knows what on earth this error message means, please please let me know.

around PC=0x399b0, Nondeterministic read from stack beyond stack pointer at 0x24a920
around PC=0x399c0, Nondeterministic read from stack beyond stack pointer at 0x24a900
around PC=0x399c4, Nondeterministic read from stack beyond stack pointer at 0x24a8f8
around PC=0x39cdc, Nondeterministic read from stack beyond stack pointer at 0x24a920
around PC=0x399b0, Nondeterministic read from stack beyond stack pointer at 0x24a930
around PC=0x399c0, Nondeterministic read from stack beyond stack pointer at 0x24a910
around PC=0x399c4, Nondeterministic read from stack beyond stack pointer at 0x24a908
around PC=0x39cdc, Nondeterministic read from stack beyond stack pointer at 0x24a930

And yes I did figure out that its trying to non-deterministically read from the stack beyond the stack pointer. But why?

For your information I get this after running the program successfully. It seems to be occurring after my code finishes executing, which is what makes it so weird.