LLDB crash

wjens wrote> Also, since launchd needs to run my XPC server, how does one go about debugging this? I didn't think I could start my XPC server from xcode because only launchd could bind the Mach service. Is there a preferred way to build/debug a LaunchAgent that hosts an XPC Mach service?While I couldn't get Xcode to attach to the XPC Mach service I'm working on through the method described this this post by ktam2, you can, however, also attempt to attach the lldb debugger to the XPC service Launch Agent at the command line with:launchctl attach -s gui/UID_ofLoggedInUser/labelOfXPCLaunchAgentRefer to the launchctl(1) man page. Also, the WaitForDebugger key is mentioned in the launchd.plist(5) man page.> Finally, do these programs need to be signed with my Developer ID (can you even sign command line programs)?You can Code Sign and Sandbox a single file executable by embedding an info.plist into it. In the Target’s Build Settings in the Other Linker Flags field, add the following to get the info.

I think you would include the parts of the UIViewController that you want to use in your protocol definition. For example, if you want your helper to have access to the view property, you would do something like this:protocol MailProtocol { var view: UIView! { get set } func mailDone() } class MyVC: UIViewController, MailProtocol { var mailHelper: MyHelper! override func viewDidLoad() { super.viewDidLoad() self.mailHelper = MyHelper(delegate: self) } func mailDone() { print(done) } } class MyHelper { let delegate: MailProtocol! init(delegate: MailProtocol) { self.delegate = delegate print(delegate.view) // for testing only delegate.mailDone() // for testing only } }However, I tried this in Xcode 7 beta 2, and when I type anything the REPL (or something) keeps crashing (i.e. code goes all black for a few seconds, get error message at top of of the source window). Compiling gives this error:SIL verification failed: return value type does not match return type of function: functionResultType == instResu

Third party crash reporting (Crashlytics, Parse et al) seems more reliable, although they don't catch everything either - for example an 0x8badf00d watchdog timeout if the crash reporting framework isn't initialized yet before the app is killed. I do get a LOT more crashes reported now that I'm using Parse.I liked it better before, when I was in blissful ignorance that everything was running perfectly 😀

Can you please file a bug report for this crash and let us know what the bug number is?Thanks!

I am also facing this problem. I have `Integer 64` property. When I assign to this property than application crashes with EXC_BAD_ACCESS(code=1, address=0x28).

Sure, filed bug # 21568805. The editor crash / compile error does not occur if you remove the set requirement from the protocol:protocol MailProtocol { var view: UIView! { get } func mailDone() -> Void }I added this info to the bug after it was originally submitted.

Yikes. Can you file a bug report with a crash log attached (from Console.app) and post the radar number here? I'll take a look.

Honestly, if you want a notification-style model to work properly, the objects observing probably should be classes.The observers need to have a stable identity, so that there is a valid target for the callback.The observers need to allow the notification center object to keep a reference to them rather than a copy of them, so that the observer is the original object.The observers need a way to deregister themselves when they go out of scope, so that the notification center doesn't try to access a deallocated observer.There are things that structs are great at... the qualities listed above are not any of those things.Using classes for types that need to listen for notifications, and using the existing NSNotification system is just simpler in most cases.You can use a unique-per-instance generated String as the sender for the notifications, if the property you are observing belongs to something that ought to be a struct, in order to match notifications originating from a particular struct instance.But trying to

phone app crash with my sim free iphone6 plus and ios9beta2. But non sim free iphone6 won't crash.

Okay I'm stuck on a part with the code like you know how splashy fish and flappy bird make the game over sound when you die and the sound when you tap it the bird makes a sound I'm trying to do something like that, but I can't figure out how I'm stuck trying to make it where when you crash it makes a crash noise and game over and I'm also trying to get it to where you can tap it and it makes a noise when you tap I have the audio I just don't know how to input it.import SpriteKitclass GameScene: SKScene, SKPhysicsContactDelegate { var score = 0 var scoreLabel = SKLabelNode() var gameOverLabel = SKLabelNode() var goat = SKSpriteNode() var nite = SKSpriteNode() var labelHolder = SKSpriteNode() let goatGroup:UInt32 = 1 let objectGroup:UInt32 = 2 let gapGroup:UInt32 = 0 << 3 let playPopAction = SKAction.playSoundFileNamed(Powerup.mp3, waitForCompletion: false) var gameOver = 0 var movingObjects = SKNode() override func didMoveToView(view: SKView) { self.physicsWorld.contactDelegate = self s