LLDB crash

Since updating to the second beta in El Capitan Final Cut Pro crashes each time I attempt to open it.

I am having an issue with using Activity tracing with Swift. After doing some reading I found out that one way to use activity tracing in Swift is by writing an Objective-C wrapper which the Swift classes can call. However there seems to be a problem/limitation with this approach. That is,if we write a wrapper with a method say as follows- (void)logTrace:(NSString *) eventName { os_trace(“%@“, eventName); // This will not work}The above code will not work since the documentation says that we cannot use format specifiers except %d inside os_trace(“”). This will mean that we will have to write separate methods for each event being traced like the following:- (void)logConfigureLoginButtonPressed { os_trace(“Configure Login Button Pressed); // This will work}And call this method from the Swift class, this however doesn’t seem to be a very efficient way for tracing since the wraper will have a lot of methods as I add trace messages to my project.Has anyone else faced ths issue. Is there a better workaround or any

I am puzzled by this - seems to be new. Running XCode7 (beta1 and beta2 see same outcome)I am calling...if let metadataItem = metadataItem { if let value = metadataItem.valueForAttribute(NSMetadataUbiquitousItemIsUploadingKey) as? NSNumber <- EXC_BAD_ACCESS { return Bool(value) } }Seeing a hard crash when valueForAttribute is called. metadataItem appears perfectly valid. Calling the same method with any string does the same.Not happening in the simulator.

Anyone is having the same bug? The Mail app crashes every time I try to open it.

I'm getting the following error..------------------------------------------------------------2015-06-24 10:57:50.715 Metal_Touch2[472:68884] Metal GPU Frame Capture Enabled2015-06-24 10:57:50.717 Metal_Touch2[472:68884]failed assertion _interposeHandle != NULL at/BuildRoot/Library/Caches/com.apple.xbs/Sources/Metal/Metal-54.7/Framework/MTLDevice.mm:110 MTLInitializeInterpose(lldb)this happens when i first call. self.device = MTLCreateSystemDefaultDevice()------------------------------------------------------------I developed this app using Xcode 6 - it is written in Swift & Metal.I upgraded to El CapitanI upgraded to Xcode 7 BetaI recompiled (now Swift 2.0) all my programs and tested on my iPad Air (Model 1474)targeting iOS 8.3 - all work fine. [this includes 25 applications using 35 different shaders]------------------------------------------------------------I installed the iOS 9 beta 2 software.[iOS 9 beta 2 - iPad Air (Model A1474) - 13A4280e]Still targeting iOS 8.3 my application builds and

As everyone knows, XCode 7 now has a feature of defining NSManagedObject subclass properties into an Extension (example: Event+CoreDataProperties.swift). But in my case I use primitive types and when I run the app in simulator and attempt to set the primitive property (example: event.status = 2), the app crashes with EXC_BAD_ACCESS(code=1, address=0x28).However if I copy these properties from the extension to the class Event file - everything works fine. Not sure if this is an expected behavior or a bug.Any pointers will be deeply appreciated.

I'm getting a crash out in the field that reports EXC_BREAKPOINT UNKNOWN at 0x0000defe.Is there a special significance to this address, like there is with 0x0badf00d?

I am seeing a problem with iOS9 beta2. Didn't have it before.if let metadataItem = metadataItem { if let value = metadataItem.valueForAttribute(NSMetadataUbiquitousItemIsUploadingKey) as? NSNumber <- EXC_BAD_ACCESS { return Bool(value) } }calling valueForAttribute causes EXC_BAD_ACCESS. Turning on zombies, the same call generates this warning in the log.-[NSMetadataQuery _allAttributes]: message sent to deallocated instance 0x1370968a0It's as if the metadataItem was retaining a pointer and making a call to the query which generated it.At this point in my code, the query has been deallocated.