|
Re: Motor declarations break analog module
Without viewing the code I'm just guessing, but in my experience, when commenting out code which initializes something and noting bizarre side-effects, it is often useful to look at your compiler warnings or at the code directly for uninitialized variables. The compiler tends to allocate stack variables one after the other except that the optimizer may scramble the order or double up variable declarations. Anyway, if you have an uninitialized variable, these allocations can give your code different behaviors based upon the value that other function calls leave on the stack.
Greg McKaskle
|