unable to execute command: Segmentation fault: 11 swift frontend command failed due to signal (use -v to see invocation)

问题

I have an iOS swift program that compiles and runs fine on Xcode Beta2. When I downloaded beta4, I got a few syntax errors for the new swift language which I corrected. I now get this error:

<unknown>:0: error: unable to execute command: Segmentation fault: 11
<unknown>:0: error: swift frontend command failed due to signal (use -v to see invocation)

The problem is that it does not tell me where this error is so that I can further troubleshoot it. Where can I type -v in order to "see the invocation" and troubleshoot further? Without this, there is absolute no way to figure out the problem. Thanks in advance.

回答1:

Here's how I was able to find out what the problem was:

Click on the issue in the issue navigator (⌘ + 4, then click on the line with the red ! at the start)
At the bottom of the file that appears, there should be a line that says something like:

1. While emitting IR SIL function @_TToZFC4Down8Resource12getInstancesfMS0_U__FTSS6paramsGVSs10DictionarySSPSs9AnyObject__9onSuccessGSqFGSaQ__T__7onErrorGSqFT5errorCSo7NSError8responseGSqCSo17NSHTTPURLResponse__T___T_ for 'getInstances' at /path/to/file.swift:112:5

The location where your error occurred is at the end of that line. (In this case, on line 112 of file.swift in getInstances).

回答2:

I was trying to add the PayPal framework to my iOS Project (Xcode 7.2 and Objective C language). When building it did not throw any error, but when I tried to archive the Project and make the IPA, I was getting that error

unable to execute command: Segmentation fault: 11

Screenshot:

After struggling for a long time, I disabled the Bitcode in Project's Target > Build Settings > Enable Bitcode. Now the project can be archived. Please check the following screenshot.

回答3:

Can't really give a straight solution on this (although I'm sure it's an Apple bug), but I just came across the exact same error message and happen to solve it. Here's what I did:

In General

Comment out recently changed Swift code (check commits) until the app compiles again
Command-click each called method in the failing line and check if there could be an ambiguity

My Example

In my case (I was using the XMPPFramework written in Objective-C) the failing code looked like this:

for roomMessage: XMPPRoomMessage in self.messages {
    let slices = split(roomMessage.nickname(), { $0 == "_" }, allowEmptySlices: false)
}

Once I replaced roomMessage.nickname() with "0_test" the code didn't fail any more. So I command-clicked the method nickname() (twice) and here's what I saw:

My guess was that the Swift 1.1 compiler has problems with figuring out which method to call if the exact type of an object is not clear. So I made the type of roomMessage explicit and got another error which I fixed by removing the braces behind the nickname() method call. This made my app build again. Here's the working code:

for roomMessage: XMPPRoomMessageCoreDataStorageObject in self.messages {
    let slices = split(roomMessage.nickname, { $0 == "_" }, allowEmptySlices: false)
}

I hope this helps someone out there to investigate the issue more quickly than I did.

回答4:

In my case this error because I use Class name for variable

var MYClass : MYClass {
    get {
        return.....
    }
}

And this fixes my problem

var myClass : MYClass {
    get {
        return.....
    }
}

回答5:

I also had the same problem,

when I cleaned the derived data
Remove all removed derived data from Trash as well.
Stop Xcode, restart it and clean build

It should be fixed now.

回答6:

My problem was that I tried to mimic static variables with the so-called module approach (the Module design pattern). So, I had something like that (just a simple static reference to an operation queue declared at the level of a swift file):

let globalQueue: NSOperationQueue = {
    let queue = NSOperationQueue()
    queue.suspended = false
    queue.maxConcurrentOperationCount = NSOperationQueueDefaultMaxConcurrentOperationCount
    return queue
}()

So, that worked fine in Xcode 6.x.x, but ceased to compile in Xcode 7beta. Just want you guys to be aware of it. P.S. In general, I managed to find out what was wrong from the logs (see the screenshot attached). Hope this saves you some time.

回答7:

I got Segmentation fault when I called a protocol function the same protocols extension.

I had a code something in the line with this:

protocol Rotatable {
    func rotate() -> Self
}

extension Rotatable {
    func rotate(steps: Int) {
        for _ 0..<steps { self.rotate() }
    }
}

When I later made an object and declared that it would follow the Rotatable protocol I got Segmentation fault 11 and the program crashed.

Ex: this would cause Segmentation fault and crash Xcode

struct SomeStruct : Rotatable {

}

If I however first implemented the function rotate() in SomeStruct and then afterwards declared that it conformed to Rotatable there where no problem.

回答8:

I had a similar today and tried the steps described here including removing files I had recently modified. Nothing seemed to work. I tried something that had been suggested when SourceKit would crash in Xcode.

I when into the derived data directory and deleted everything. The location is listed under "Preferences -> Locations -> Derived Data" There is an arrow icon right next to the path which opens finder with that directory selected. Select all the directories inside and delete them. Close Xcode and Reopen it. That made the problem disappear for me.

I think that some intermediate file is getting corrupted and the compiler does not know how to handle it.

回答9:

I get this error because a silly mistake!!

in a class I defined

var url: String!?

So it seems that this description is a multiple & generic error for a lot of reasons!!

回答10:

I did answer in "Swift compiler segmentation fault when building"

I had this error too, and i fixed like this:

check your project and find out which files are using twice and remove one, or delete all and re-add them.

Errors in my xCode

:0: error: filename "AttributedString.swift" used twice: '/Users/.../CNJOB/CNJOB/AttributedString.swift' and '/Users/.../CNJOB/CNJOB/AttributedString.swift'

:0: note: filenames are used to distinguish private declarations with the same name

:0: error: filename "APIClient.swift" used twice: '/Users/.../CNJOB/CNJOB/APIClient.swift' and '/Users/.../CNJOB/CNJOB/APIClient.swift'

:0: note: filenames are used to distinguish private declarations with the same name

Command /Applications/Xcode 3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 1

回答11:

For me it's caused by adding the swift files to different targets (today extension in my case).

回答12:

I forgot to add one @end after @implementation in a .m file that had multiple classes in it. Something like:

@implementation Adjust

@end

@implementation Data //@end For this class was missing 


@implementation Create

@end

回答13:

I got this bug because of line

self.textView.inputAccessoryView = self.toolbarItems;

If you delete it the error will gone.

My steps: 1)

Deleted Derived data
Cleared build folder Didn't help
Copied class files to another folder as backup and commented everything in this class. Error gone.
Commented code blocks one by one until build was success.

回答14:

For me the problem was mixing Generics, Extensions, and @objc.

It turns out Xcode doesn't like having @objc inside extensions of generic classes:

class FaultyClass<T: TypeValidator>: UIControl where T.ItemType == String {
}

extension FaultyClass: UITextFieldDelegate {
    func textFieldDidEndEditing(_ textField: UITextField) {
    }
}

The above code gives the error @objc is not supported within extensions of generic classes. So I moved the method to the class itself but didn't delete the empty extension. This got rid of the error but when I compiled the project I got the segmentation fault.

The solution was to move UITextFieldDelegate to the class declaration.

class GoodClass: <T: TypeValidator>: UIControl, UITextFieldDelegate where T.ItemType == String {

// MARK: - TextFieldDelegate
    func textFieldDidEndEditing(_ textField: UITextField) {
    }
}

回答15:

My problem was in methods signatures:

func setCategory(categoryId: Int?, subcategoryId: Int?) -> FilterSettings {

func changeCategory(categoryId: Int?, subcategoryId: Int?, handler: @escaping (Int) -> ()) {

I don't get why compiler cannot handle such declarations.

回答16:

In my case it was because of an inappropriate inout in the function parameters. So I suggest you to look for that as well.

回答17:

For me it was something similar to what @LuisCien described in this answer https://stackoverflow.com/a/42803582/4075379

I didn't have any generics or @objc tags, but it was these lines of code that were causing the segmentation fault:

public extension CGFloat {
    /// Whether this number is between `other - tolerance` and `other + tolerance`
    func isEqual(to other: CGFloat, tolerance: CGFloat) -> Bool {
        return (other - tolerance...other + tolerance).contains(self)
    }
}

i.e. an extension on a primarily Objective-C primary type? Very luckily, I was able to delete those lines because the project wasn't using anymore. That fixed the issue.

回答18:

I ran into a similar problem when switching from beta2 to beta4. I hope these instructions are helpful.

Clean

then

Build

来源：https://stackoverflow.com/questions/25007755/unable-to-execute-command-segmentation-fault-11-swift-frontend-command-failed

标签

ios

xcode

segmentation-fault

swift