Moderator
Posts: 2362 from 2003/2/24
Without acces to the called functions and detailed debug-log it's really down to stabbing in the dark...
My guess would be that one of the functions does something really nasty like accesing an array past it's size and therefore trashes memory.
If this happens on stack (read with an array defined in the function) it might even kille the return address.
Solution:
Clean out those functions till they do nothing at all (or your code stops crashing).
And remember 99.9% of all computer-errors are between keyboard and monitor