I'm making the following assumptions, are they correct?1) The ultimate cause of the errors must be because something somewhere in my application is corrupting the data memory (I assume that program memory can't get corrupted?)2) The errors are probably still present in my small test sketches but they don't show up because the corruption that is occurring is only effecting un-allocated memory that isn't being used by anything else. - it's only as the size of the overall application builds and more memory gets used that the corruption problems starts to corrupt memory that actually being used.3) If I know a particular function hasn't been called before a problem occurs, then I can be sure that function hasn't corrupted anything?4) The most likely cause of a problem is likely to be setting an array index outside of it's bounds i.e. temp=y where x is 10 and the array only consists of 5 elements.5) Number variables (i.e. ints, longs and floats etc) are unlikely to cause corruption because if they overflow they will 'wrap around' rather than corrupt other memory.6) Any code that runs could be corrupting something, just because the error appears in function X doesn't mean that function X is the cause.
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16