6 Replies Latest reply: May 16, 2010 4:17 PM by doofusdan
Paulo Rodriguez Level 1 Level 1 (0 points)
After installing Xcode 3.2, the 10.6 debugger gives some strange results.

I created a new project using: Application->Command Line Tool -> C++ stdc++

Pasted in the code from cplusplus.com for istringstream.

Here is the simple code :

// using istringstream constructors.
#include <iostream>
#include <sstream>
#include <string>
using namespace std;

int main () {

int n,val;
string stringvalues;

stringvalues = "125 320 512 750 333";
istringstream iss (stringvalues,istringstream::in);

for (n=0; n<5; n++)
iss >> val;
cout << val*2 << endl;

return 0;

Console Results for: 10.6|Debug|X86_64 or i386:

If set to :
10.5|Release or Debug| x86_64 or i386
10.6|Release| x86_64 or i386
Console Results:


Compiling with 10.6 Debug seems to have a problem. I tried doing a clean install of SL 10.6 and clean install of Xcode 3.2, but get same results.

Any suggestions?

17" Macbook pro (late 2007)
  • etresoft Level 7 Level 7 (25,870 points)
    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).
  • etresoft Level 7 Level 7 (25,870 points)
    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:

    #include <iostream>
    #include <sstream>
    #include <string>

    #define GLIBCXX_DEBUGDEFINED "<undefined>"

    int main()
    std::string svalue("42");
    std::istringstream in(svalue);

    int value;

    in >> value;

    std::cout << "Original value was: " << svalue << std::endl;

    << "With GLIBCXXDEBUG="
    << " value is "
    << value << std::endl;

    return 0;

    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".
  • Paulo Rodriguez Level 1 Level 1 (0 points)
    Thanks. That fixed it.
  • CraigularB Level 1 Level 1 (0 points)
    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!
  • yanhua037 Level 1 Level 1 (0 points)
    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!
  • doofusdan Level 1 Level 1 (0 points)
    Ditto - this is my first time using Xcode for C++ (I've used it before for Obj-C/iPhone SDK) and I was just about to switch back to Visual Studio!