Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?
Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?
- Subject: Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?
- From: Chris Espinosa <email@hidden>
- Date: Fri, 5 Dec 2008 20:25:44 -0800
On Dec 5, 2008, at 5:31 PM, Shawn Erickson wrote: On Fri, Dec 5, 2008 at 6:38 AM, Sean McBride <email@hidden> wrote:
Matt Gough (email@hidden) on 2008-12-05 3:29 AM said:
OK, so dumb question, but :
What is the STL-debug feature?
Sounds like something I wish I had on all along.
Alas, it's under-documented and under-publicised. It was added in gcc 3.3:
<http://developer.apple.com/ReleaseNotes/DeveloperTools/RN-GCC3/index.html>
It was removed in 4.2.
To bad it has been removed... it helped me track down a handful of issues in our common code core that had been causing spurious hard to debug/reproduce problems in our Windows products.
"Removed" is not quite accurate. The Standard Template Library is part of the C++ dynamic library support that is built into Mac OS X. Because gcc 4.2 shipped after Leopard did, it still uses Leopard's C++ libraries, but it's not compatible with the Debug mode in those libraries.
A hypothetical future version of Mac OS X that had the gcc 4.2 standard C++ libraries built in would be compatible with the _GLIBCXX_DEBUG mode of gcc 4.2. If you'd like to track the progress of this, file a bug at bugreporter.apple.com and request it be made a duplicate of bug #5011519.
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden