Quote:
Originally Posted by Toni Wilen
Only difference is extra long word in stack, it shouldn't have any effect unless you previously used every byte of the stack which is very unlikely 
After initial break, add dummy breakpoint (f 0 for example), then g. When first invalid access comes, use H command to see history of executed commands. (up to last 500 instructions). It should help to find out what happened.
EDIT: stack frame commands may also help. |
There must be something wrong with my setup or something. I just seem to get invalid accesses in random locations and H doesn't really show anything useful, and a d at the break location shows garbage instructions (Doesn't seem to match up with my code at all).
In fact depending on the config I use (A3000/A4000/Ram config etc) the invalid access hits are totally different.