Clang vs. gcc and random crashes
Clang vs. gcc and random crashes
- Subject: Clang vs. gcc and random crashes
- From: Michael Domino <email@hidden>
- Date: Wed, 25 Mar 2015 14:38:36 +0000
- Thread-topic: Clang vs. gcc and random crashes
|
Hi all,
I’m building my OS X product using Xcode 3, on 10.6, using 10.5 as the base and deployment SDK. It’s been very stable on 10.5 through 10.9. On 10.10 we’ve been seeing a lot of random crashing. Management is reluctant to make any changes to the
build process, i.e. move to Xcode 6.2 on 10.10, using a base SDK of 10.10 and a deployment SDK of 10.5, which I would like to do, but I need some good reasons for doing so.
Bug filed with gcc:
==========
It seems when a thread is finished, its thread cleanup routine is called before destructors of TLS(Thread Local Storage) variables are called and it causes (possible) segmentation faults.
This problem happens only on OSX. When I tried the same C++ code on Ubuntu12.04 with g++-4.8.1. There was no problem.
I also tried with clang++-3.3 on OSX. There was no problem either.
==========
So the question is: besides the problem in the gcc bug report, can continuing to build with Xcode 3 using gcc with a 10.5 base SDK cause instability (random crashing) on 10.10?
Thanks,
Michael Domino
|
_______________________________________________
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