Quote Originally Posted by Salem View Post
I don't think it's possible for you to categorically say that "this bug" caused "that lockup".

Rather than generating map files, it may be easier to disassemble the code for that function to find out what memory locations are overlapping, then construct code behaviour from that point.

For example, if the last array slot was also the loop counter, then writing zero to the last array slot would also reset the loop variable back to the beginning. That would indeed lock up the code in a never ending loop.

But who says this is the only bug in the code?
If you found one by inspection, I'd bet a dime-a-dozen there will be more in the code.
our hope is to demonstrate that the variable that regulates a loop is continuosly resetted and this stuck the machine that then will be resetted by the WDG.. but you are right we'll surely keep on debugging the code ..

thanx