On Thu, Nov 17, 2011 at 7:40 AM, JMGross <msp...@grossibaer.de> wrote: > > Von: Sergio Campamá > >> I'm developing an app that uses heavily printf for debugging... Now, when >> activated (through a DEBUG macro), the app crashes very rapidly, being >> random the moment it crashes (almost always it crashes mid sentence)... > > One thing I discovered with printf is that the compiler puts the parameters > on stack, > but when optimization is on, it does not remove them from stack after the > call. > This is only done at the end of the current programming block.
The defaults that produced this behavior were changed in April, and the problem should not occur in the current supported release. http://sourceforge.net/tracker/index.php?func=detail&aid=3290923&group_id=42303&atid=432701 Peter ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
