I just checked on my system (windows build from 12/08) and everything seems to be okay. The source code for the printf function hasn't changed for 6 years. The compiler seems to generate the proper call sequence. Fine.
But I noticed that the spaces in your code snipped are followed by an 0xa0 'shift-space'. Is this intentional? Maybe the library code does what it should but your code handling the result chokes on the 0xa0? Also, the s(n)printf function use static variables while working, so the code is not reentrant. You may not use it from within an ISR as this would mess up the output from the main loop. JMGross ----- Ursprüngliche Nachricht ----- Von: Jordi Soucheiron > snprintf(debugbuf, 256, " + Accelerometer Started\n"); > But instead of moving the string to the debugbuf keeps the same > information just as if " + Accelerometer Started\n" was a null > string.
