I am trying to execute this very basic code in the Lua VM:
for i=1,1000 do print(i) end
What happens is that after “i” reaches 380+, the modem resets, without any warning/error.
When checking the backtrace, the following errors show up:
Current OAT task index 0
ARM Data Abort caught at 0028723A, Current Task 1D by CP15
The 0028723a address seems to map to the luaV_execute function.
I could be caused by a memory leak, but it’s just a guess.
I am using oatlua revision 97 on a Fastrack Supreme 10 modem (compiled with a 256KB memory model).
The oatlua library was built without any debug information to save memory.
A fix for this problem would be great, because it really impacts our project.