pantaz:
I ran across this recently --
Arduino compiler problem with #ifdefs solved. | Sub-Etha SoftwareI can't say if it applies to your situation, but it could be worth a look.
Thanks for the pointer, I'll file that one away in my bag of tricks, I'll be victimized by that bug at some point in the future.
Unfortunately it's not a lack of definitions that's getting me. It appears to be defining something it should not. But I don't know how best to debug from here. The more I try to simplify the sketch, the smaller the wasted space is. Until I have very little left of my sketch and close to 0 bytes wasted.
still looking for ideas if anyone has them. Or cares to look at my sketch and see if they can confirm or workaround it. My sketch uses too much sram for the uno, so if I compile with debug on, it won't even boot up the sketch. The sram just gets gridlocked. According to my debugger, debugging consumes an additional 3.7k of sram 