mixing compiler

I am wondering if it is possible to link a c++ program compiled with gcc4.2 with a shared c++ library that is compiled in a later version like gcc4.5.

I've tried to do this, but have run into some different kind of problems. When compiling the shared library gcc5.3 I get a message saying:

*"malloc: error for object 0x7fff707d2500: pointer being freed was not allocated set a breakpoint in malloc_error_break to debug"*.

If I try to compile the shared library with gcc4.6 I get really strange behaviour. The std::stringstream class is not working correctly. The resulting string is empty after writing to the stream.

Is it possible to do this? Or am I trying something that is impossible? I was hoping that this was possible since I'm linking the lib dynamically. Btw I'm开发者_开发技巧 running on MacOSX.

BR

Beginning with gcc 3.0, g++ follows the Itanium ABI, so in theory there should be no problem. However, g++ 4.2 has CXXABI_1.3.1 whereas g++ 4.5 has CXXABI_1.3.4 (see here). Therefore I'd be careful. One does not bump up revision numbers if there are no differences.

Further, the glibc++ has gone through 5 revisions between those versions, which may be one reason why you see std::stringstream do funny things.

Lastly, there exist many config options (such as for example making strings fully dynamic or not) which affect the behaviour and compatibility of the standard library directly. Given two (random, unknown) builds, you cannot even know that they have the same config options.

In my experience the ABI compatibility means that C++ libraries can link to each-other without problems.

However, because C++ uses so many inline functions this doesn't mean much.

If the Standard C++ Library used all inline functions or used all library functions then you could use code compiled with older versions of GCC with newer versions.

But it doesn't. The library mixes inline and external library code. This means that if something is changed in std::string, or std::vector or locales or whatever, then the inlined code from the old GCC is out of sync with the library code linked from the new GCC.