This discussion is archived
9101 Views 6 Replies Latest reply: May 16, 2010 4:17 PM by doofusdan
Currently Being ModeratedSep 18, 2009 4:21 PM (in response to Paulo Rodriguez)Double-click on your Xcode target, select the Build tab, scroll down to "GCC 4.2 - Preprocessing" and delete what is in "Preprocessor Macros". At first, these values just seemed to cause some harmless warning messages, but apparently they also change how software runs (or doesn't).MacBook, Mac OS X (10.5.7), 2.0 Ghz/4GB Ram/200 HD
Currently Being ModeratedSep 18, 2009 4:55 PM (in response to Paulo Rodriguez)Someone in another thread has already filed a bug about this, but your example was so sweet that I just couldn't resist filing another. I edited your code just a bit to simply and clearly show the bug:
#define GLIBCXX_DEBUGDEFINED "1"
#define GLIBCXX_DEBUGDEFINED "<undefined>"
in >> value;
std::cout << "Original value was: " << svalue << std::endl;
<< "With GLIBCXXDEBUG="
<< " value is "
<< value << std::endl;
Try running with default debug and release settings. Then try debug bug without these macros.
My bug will certainly be rejected as a duplicate.
I am beginning to take a perverse pleasure in filing 10.6 bugs.
But this is a very important plot point - in 10.6 you must remove the macros "GLIBCXXDEBUG=1 GLIBCXX_DEBUGPEDANTIC=1".MacBook, Mac OS X (10.5.7), 2.0 Ghz/4GB Ram/200 HD
Currently Being ModeratedOct 15, 2009 5:07 PM (in response to etresoft)I just wanted to say thanks to this post and this thread in general, I found this when I ran into this exact error while working on a school project. So, thanks for the fix!Macbook Pro 4,1, Mac OS X (10.6.1), iPhone 3GS OS 3.0
Currently Being ModeratedJan 2, 2010 3:39 PM (in response to etresoft)Thank you so much! I was working on a program which read the file and the same problem occurs. But it's fixed now.
So do I just remove the code in the Preprocessor Macros? Will it cause any problem in the future? thanks a lot!Mac Pro 13', Mac OS X (10.6.2), 2.26 GHZ 2GB RAM