iOS Xcode compile error: unable to execute command: Segmentation fault: 11

Question

I have a project which compiled perfectly in the past, but after the last Xcode update (6.3.2) I get a compile error whenever I try to run it directly on a device. Building and Running it in the simulator works fine. The Archive function works fine as well. But no matter what device I connect or what iOS version the device is running, I always get the same compile error:

Stack dump:

0.  /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS8.3.sdk/System/Library/Frameworks/CoreImage.framework/Headers/CIFilter.h:221:39: current parser token 'NS_REQUIRES_NIL_TERMINATION'
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see invocation)
Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)
Target: arm-apple-darwin14.3.0
Thread model: posix
clang: note: diagnostic msg: PLEASE submit a bug report to http://developer.apple.com/bugreporter/ and include the crash backtrace, preprocessed source, and associated run script.
clang: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /var/folders/p5/2yjs4f055hb0vvgl12yvj38r0000gq/T/SmallAdsSystem-a86b3e.m
clang: note: diagnostic msg: /var/folders/p5/2yjs4f055hb0vvgl12yvj38r0000gq/T/SmallAdsSystem-a86b3e.cache
clang: note: diagnostic msg: /var/folders/p5/2yjs4f055hb0vvgl12yvj38r0000gq/T/SmallAdsSystem-a86b3e.sh
clang: note: diagnostic msg: 

********************

It shows me random files that I'm supposed to submit to the bug report.
I haven't made any code changes from a working version to the version causing the current problems and I even reverted to an earlier version which is live and running in the Appstore but still the same error.
I have deleted xcode and installed again trough the app store
I tried making changes to my code to maybe pinpoint any problems but since the source file of the problem changes every time, I don't really think anymore that it has anything to do with my code.

This is driving me mad. Any help is much appreciated

Did you do this? "diagnostic msg: PLEASE submit a bug report to developer.apple.com/bugreporter and include the crash backtrace, preprocessed source, and associated run script. clang: note: diagnostic msg:" — picciano
– picciano, Commented Jun 1, 2015 at 14:58
No, not yet. Wanted to know if it's just simply my fault first. — Cane
– Cane, Commented Jun 1, 2015 at 15:18
Picciano is correct: you should always report a compiler crash, which can’t be your fault. (Though as user2444342 notes, you can sometimes work around the crash by fiddling with your code.) VD Patel: GCC was removed from Xcode years ago. (The last GPL 2 version was getting quite old, and Apple can’t use any GPL 3 version.) — Flash Sheridan
– Flash Sheridan, Commented Apr 9, 2016 at 16:02

hmatar · Accepted Answer · 2017-05-10 09:20:19Z

33

I tried to add the paypal framework to my iOS Project (Using Xcode 7.2 and Objective-C language), When building it is not giving any error, but when I try to archive the Project and trying to make the IPA, I am getting that Error

unable to execute command: Segmentation fault: 11

Screenshot:

After huge trying I have disabled the Bitcode in Project's Target->Build Settings->Enable Bitcode. Now the build can be achieved. Please check the following screenshot.

edited May 10, 2017 at 9:20

hmatar

2,4372 gold badges19 silver badges27 bronze badges

answered Apr 8, 2016 at 8:38

Manab Kumar Mal

21.5k5 gold badges34 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Bhavin Ramani Over a year ago

will there any issue if I put it in app store?

Manab Kumar Mal Over a year ago

Hi @BhavinRamani I have tried to make that on 2-3 projects for Google Sign up by WebView, and paypal framework, But till now app store testers did not respond me anything for that, I mean still now the App can be lived by that change. I do not know later on they change anything or not.

Bhavin Ramani Over a year ago

Your answer helped me. I got error while archive the project not in run time after integrated facebook analytics in my app. Thanks for your reply. 😀

mkll Over a year ago

It helped me. Fresh new project, Xcode 7.2, OS X 10.10.5, archiving was lead to segmentation fault. Disabled bitcode, and oops, archiving done.

徐振甲 · Accepted Answer · 2018-02-03 07:15:09Z

17

I found a fix for my problem:

I'm using a virtual machine and opened the project directly in the shared folder. I moved the project to the documents and now it works!

answered Feb 3, 2018 at 7:15

徐振甲

1711 silver badge2 bronze badges

2 Comments

green0range Over a year ago

Closing and reopening project worked... I feel dumb, but thanks!

Volker Simonis Over a year ago

Had the same problem. It seems that clang indeed can not handle sources in a shared folder. After copying the sources into a local folder within the virtual machine, everything worked.

Vikram Belde · Accepted Answer · 2017-01-04 01:42:35Z

6

unable to execute command: Segmentation fault: 11.

I was able to turn off the bitcode and able to achieve the ipa. An in depth of what bitcode means can be seen here

answered Jan 4, 2017 at 1:42

Vikram Belde

1,1989 silver badges16 bronze badges

1 Comment

Roberto Rodriguez Over a year ago

It worked, but I also needed to remove the project from WorkSpace and open it again.

Biga · Accepted Answer · 2016-07-15 08:40:42Z

4

We've just realized that segfault was caused by invalid unicode characters in our sources.

answered Jul 15, 2016 at 8:40

Biga

5814 silver badges10 bronze badges

Comments

Stephen Rauch · Accepted Answer · 2018-02-15 03:33:01Z

3

If you are using a virtual machine, then copy the files inside the virtual machine, don't import from your shared files, and it will work.

edited Feb 15, 2018 at 3:33

Stephen Rauch♦

50.1k32 gold badges118 silver badges143 bronze badges

answered Feb 15, 2018 at 3:11

Hamada AL

313 bronze badges

Comments

user2444342 · Accepted Answer · 2015-06-27 17:59:53Z

I had the exact same problem. In my case I looked at the offending file and played around with it. I was able to resolve the error by commenting out a giant NSDictionary declaration:

 NSDictionary* glyphNameToUnicode = [[NSDictionary alloc] initWithObjectsAndKeys:
                                    @"A", @"A",
                                    @"\u00C6", @"AE",
                                    @"\u01FC", @"AEacute",
                                    @"\u01E2", @"AEmacron",

This thing had probably 300 lines maybe more. Instead I moved the declaration into a file and loaded the dictionary from the file. Not sure if that helps, but in my case those files were not random...

Its deff a bug with xcode though...

SmarterSusheel · Accepted Answer · 2016-09-09 12:13:54Z

2

Pods are provided xcode/.... path for installation from git and i installed xcode 7.3.1 and its named like xcode3 so i face this type of error but when i renamed it to xcode then this error is solved for me.

So In summary, First of all please check your xcode name in application section.

If it is not xcode then please rename it to xcode and try to run your app.

edited Sep 9, 2016 at 12:13

answered Sep 9, 2016 at 7:28

SmarterSusheel

1692 silver badges15 bronze badges

2 Comments

Joshua Nozzi Over a year ago

Thanks, this put me on the right track and I asked the moderator to undelete it. See my answer (Sept 29, '16) for details.

SmarterSusheel Over a year ago

Thanks @JoshuaNozzi for understand it.

Cane · Accepted Answer · 2015-09-03 09:01:58Z

1

Apparently it was a bug in my Xcode version. Had to revert to an old one and everything worked again. With the newest update everything was working ok again.

answered Sep 3, 2015 at 9:01

Cane

1991 gold badge1 silver badge6 bronze badges

Comments

Joshua Nozzi · Accepted Answer · 2016-09-29 19:16:50Z

1

In order to solve a problem (a known bug closed as a duplicate as of this writing) that caused apps built under 10.12 (macOS Sierra) to fail to launch under 10.9 (even when they'd done so without trouble previously), I'd installed 10.11 and Xcode 7.3.1 under a VMWare instance. Xcode (due to laziness on my part) was copied to the Desktop.

After reading SmarterSusheel's answer regarding a renamed Xcode, it dawned on me it may be path-related, so I moved Xcode to /Applications and tried again. Problem (mostly) solved. I say "mostly" because I also had to copy my project folder into the VMWare instance since it seemed to have issues building under the shared folder as well.

edited Sep 29, 2016 at 19:16

answered Sep 29, 2016 at 17:06

Joshua Nozzi

61.3k14 gold badges143 silver badges136 bronze badges

Comments

llama591 · Accepted Answer · 2017-05-11 06:03:24Z

1

Setting Link-Time Optimization to NO in both Debug and Release mode is what resolved the problem for me.

answered May 11, 2017 at 6:03

llama591

4735 silver badges15 bronze badges

2 Comments

Stanislav Goryachev Over a year ago

Incremental did not work on device, but Monolithic works fine. So I used No for debug and Monolithic for Release.

ThE uSeFuL Over a year ago

@StanislavGoryachev is correct select "Whole Module" for "Compilation Mode" in "Build Settings".

Artur Kucaj · Accepted Answer · 2016-06-01 13:20:58Z

0

I was facing similar issue:

clang: error: unable to execute command: Segmentation fault: 11
clang: error: linker command failed due to signal (use -v to see invocation)

Simply updating from Xcode 7.2 to 7.3.1 has resolved the issue!

answered Jun 1, 2016 at 13:20

Artur Kucaj

1,0811 gold badge11 silver badges16 bronze badges

1 Comment

Biga Over a year ago

It helped me too. But after a while having the same problem with Xcode 7.3.1.

Raimundas Sakalauskas · Accepted Answer · 2018-06-21 11:47:04Z

0

I only had problem for i386 architecture when building for iPhone 4s simulator running 9.3

When disabling bitcode didn't work (suggested above), i tried to look at the source code. I didn't find any ascii related stuff (suggested by others), so I tried to comment out method by method until I found the offending line. For me the error was caused by this:

let keyboardSize = ((info![UIKeyboardFrameBeginUserInfoKey] as AnyObject).cgRectValue.size)

Changed it into:

let keyboardSize = (info![UIKeyboardFrameBeginUserInfoKey] as! NSValue).cgRectValue.size

answered Jun 21, 2018 at 11:47

Raimundas Sakalauskas

2,3041 gold badge24 silver badges25 bronze badges

Comments

rupesh45 · Accepted Answer · 2020-03-24 07:28:02Z

0

Quit and reopen the Xcode worked for me !

make sure you clean the build folder after reopening the Xcode !

answered Mar 24, 2020 at 7:28

rupesh45

1353 silver badges8 bronze badges

Comments

Musa almatri · Accepted Answer · 2024-03-12 08:35:03Z

0

Adding this flag -ld64 to Other Linker Flags fixed it on Xcode 15

answered Mar 12, 2024 at 8:35

Musa almatri

5,8723 gold badges37 silver badges35 bronze badges

Comments

nitin · Accepted Answer · 2016-12-14 06:42:19Z

-1

I was facing similar issue:

clang: error: unable to execute command: Segmentation fault: 11 clang: error: linker command failed due to signal (use -v to see invocation)

then i was change my Provisioning profile.

answered Dec 14, 2016 at 6:42

nitin

1

Collectives™ on Stack Overflow

iOS Xcode compile error: unable to execute command: Segmentation fault: 11

15 Answers 15

4 Comments

2 Comments

1 Comment

Comments

Comments

Comments

2 Comments

Comments

Comments

2 Comments

1 Comment

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

15 Answers 15

4 Comments

2 Comments

1 Comment

Comments

Comments

Comments

2 Comments

Comments

Comments

2 Comments

1 Comment

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related