Eureka: Command failed due to signal: Segmentation fault: 11 after adding another Pod to my project.

Created on 20 Jun 2017  路  8Comments  路  Source: xmartlabs/Eureka

Hey there, after adding another cocoapods dependency to my project. My release builds started to fail with this error:
Command failed due to signal: Segmentation fault: 11

The error log is long, but this is at the bottom of it:

While emitting IR SIL function @_TTSg5SSSSs9Equatables_C6Eureka12TextAreaCellS1_S0_8CellTypeS0_uRxS0_18InputTypeInitiablexS_rGCS0_13_TextAreaCellx_S0_13TextInputCellS0_S1_S0_13TypedCellTypeS0____TFFC6Eureka15FormatteableRowcFT3tagGSqSS__GS0_xq__U_FGSqQ__GSqSS_ for expression at [/Users/MyPcName/Desktop/IOSProjectsFolder/MyAppName/Pods/Eureka/Source/Rows/Common/FieldRow.swift:73:27 - line:80:9] RangeText="{ [unowned self] value in
            guard let v = value else { return nil }
            guard let formatter = self.formatter else { return String(v) }
            if (self.cell.textInput as? UIView)?.isFirstResponder() == true {
                return self.useFormatterDuringInput ? formatter.editingStringForObjectValue(v as! AnyObject) : String(v)
            }
            return formatter.stringForObjectValue(v as! AnyObject)
  • Environment: Eureka 1.7.0, Xcode 7.3.1 and iOS 2.3.

My question is, how can I pinpoint the exact issue here?

awaiting response

Most helpful comment

The workaround for this issue is to set the SWIFT_OPTIMIZATION_LEVEL for the Release build to "Fast [-O]" instead of "Fast, Whole Module Optimization [-Owholemodule]" (which is the default introduced in CocoaPods 1.2.1).

All 8 comments

Hey @yigitserin !
have you found a workaround for this issue ?

I have the same issue on macOS 10.12.5, Xcode 7.3.1, Eureka 1.7.0.
From my point of view the cause of this compiler issue is the casting:
self.cell.textInput as? UIView

The workaround for this issue is to set the SWIFT_OPTIMIZATION_LEVEL for the Release build to "Fast [-O]" instead of "Fast, Whole Module Optimization [-Owholemodule]" (which is the default introduced in CocoaPods 1.2.1).

I have the same issue. how to resolve it?

In my case, looks like it was something related to associatedtype. As soon as I commented it, it could compile.

This looks like a compiler issue. Does it still happen with Swift 4?

I am facing same issue with the same environment, can anyone help me out please.

I just wasted an hour fighting a similar issue in my code. It went away when I changed an [unowned self] to a [weak self].

Was this page helpful?
0 / 5 - 0 ratings