Search results for

LLDB crash

29,555 results found

Post

Replies

Boosts

Views

Activity

Illegal Instruction: 4
With optimizations on the Swift compiler of Xcode 7 now crashes with Illegal Instruction: 4. Apparently something is not yet implemented.Not yet implemented UNREACHABLE executed at /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/SILPasses/Utils/CFG.cpp:522! 0 swift 0x0000000107d93e0b llvm::sys::PrintStackTrace(__sFILE*) + 43 1 swift 0x0000000107d9454b SignalHandler(int) + 379 2 libsystem_platform.dylib 0x00007fff9110af1a _sigtramp + 26 3 libsystem_platform.dylib 0x000000000000ffff _sigtramp + 1861243135 4 swift 0x0000000107d94346 abort + 22 5 swift 0x0000000107d4de21 llvm::llvm_unreachable_internal(char const*, char const*, unsigned int) + 481 6 swift 0x000000010625b160 swift::splitEdge(swift::TermInst*, unsigned int, swift::DominanceInfo*, swift::SILLoopInfo*) + 2992 7 swift 0x000000010625b294 swift::splitEdgesFromTo(swift::SILBasicBlock*, swift::SILBasicBlock*, swift::DominanceInfo*, swift::SILLoopInfo*) + 212 8 swift 0x0000000106113dda (anonymous namespace)::Swif
2
0
1.5k
Jun ’15
Reply to Understanding Optionals
This is how I understand it:In Objective-C, all class instance variables are what would be called Optional in Swift, because all of them can potentially be nil.I have found for myself it is better to think of Swift as adding non-optionalness. Meaning, you can now declare that values will never be nil, and then not have to worry about checking if they are, or code silently failing. Although you can put in checks for this, it is not something that exists at compile time in Objective-C.The ! (implicityly unwrapped optional) was there mainly for compatibility with existing Objective-C libraries for convenience. Although many API calls could potentially return nil for some values, in practice the internal implementation prevented this from happening. By importing the call with the ! modifier, this tells you that the value will not be nil, and also points out that nothing in the complier enforces that, and if it is nil for some reason the application will crash. This made things a lot less painful in the S
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’15
iOS9: Siren and Banshee. :)
After many fails in areas like battery life, Game Center, App Compatibility, crashing, etc., I decided to revert to iOS8. I simply can't function at this point with iOS9, and unfortunately I can't afford to buy a second test device.But, despite all of that, just minutes after getting a functional iOS8 reinstall and restore, I am tempted by the Siren call to put iOS9 back on. LoL Yes, the improvements, in my mind, are THAT great. Especially on the new iPad Air 2 I had to get to replace my iPad2. Just phenomenal.So, a note to those who are on the fence about installing the beta, I don't personally think it is daily driver ready, and it will **** your soul like a banshee if you do it, but you will have a hard time ignoring the siren call once you have used it. 🙂
1
0
401
Jun ’15
Protection data didn't match
I am developing my first App to use CloudKit.I am getting Partial Failure, Server Record Changed, Protection data didn't match error on only one of a pair of CKRecords after attempting to save local changes to a custom zone.In this case, the change is modifying a CKReference type property on both CKRecords, referencing records in the same zone, using CKModifyRecordsOperation.The CKRecords that were modified, had only just been read from the server and in this case, no other App had attemtped to modify them after that load.The correct data appears to be in the sent records, including same recordChangeTag.My save method, is a series of nested blocks (maybe change to NSOperations after seeing the excelent talk at WWDC'15).The method first attempts to save, then if there are errors, update, then save again.The first save produces the protection error above, on one record, the second save produces Domain=NSCocoaErrorDomain Code=4097, NSDebugDescription=connection to service named com.apple.cloudd, if I send the to
1
0
357
Jun ’15
app crashes at launch as release build on iPhone - but debugging is fine
I have imported ios-charts in my Objective-C project, and running it in debug mode is fine. However, today I tried to archive and ad-hoc distribute my app, the app crashes at launch...I have set the swift optimization to none for release mode, still no luck.I have no log or trace since it's installed on iPhone 6. I am looking for help if anything I missed...I tried to remove all swift stuff and archive, everything is as usual now. However, once I drag the swift files into my Objective-C based project, Run(debug) the app is fine. But if archive(release) and install it on iPhone, immediate crash at launch. Anything what I am missing?I am with latest Xcode and swift official release
5
0
8.6k
Jun ’15
UITapGestureRecognizer crash with Zombie?
class GameScene: SKScene { override func didMoveToView(view: SKView) { / Setup your scene here */ let pinch = UIPinchGestureRecognizer(target: self, action: handleGesture:) let rotate = UIRotationGestureRecognizer(target: self, action: handleGesture:) let pan = UIPanGestureRecognizer(target: self, action: handleGesture:) let tap = UITapGestureRecognizer(target: self, action: handleTap:) let doubleTap = UITapGestureRecognizer(target: self, action: handleTap:) pan.maximumNumberOfTouches = 1 doubleTap.numberOfTapsRequired = 2 pinch.delegate = self rotate.delegate = self pan.delegate = self tap.delegate = self doubleTap.delegate = self view.addGestureRecognizer(pinch) view.addGestureRecognizer(rotate) view.addGestureRecognizer(pan) view.addGestureRecognizer(tap) view.addGestureRecognizer(doubleTap) view.scene?.backgroundColor = UIColor.whiteColor() } override func update(currentTime: CFTimeInterval) { / Called before each frame is rendered */ } } extension GameScene: UIGestureRecognizerDelegate { func gestureReco
1
0
978
Jun ’15
Can I install iOS7 on iPhone4s? (current iOS 6.1.3)
Hi.I want to install iOS7 on my iPhone4s iOS6.1.3 installed.I downloaded install file(iPhone4,1_7.0_11A465_Restore.ipsw) and tried install, but failed.# Fail messageThe iPhone iPhone could not be restored. This device isn't eligible for the requested build.I know that can't downgrade from iOS8.My app has app crash issue on iOS7 with beacon (on iOS8 OK)How can I install iOS7 on my iPhone?
2
0
443
Jun ’15
ipad mini crash
I developed an app for all iOS devices. My app was working great in simulators, ipads and iphones, but it got crashes in ipad mini only. I have tried to run the app directly from xcode to my ipad mini, but it still crashed (no log). The app showed the launching screen, and then screen became in black. After a few seconds, apple logo came out again. The whole process just like restarting my ipad mini. I especially tested my app with ipad2, it worked very smooth.Anyone has idea what I did wrong to make this issue?
0
0
250
Jun ’15
Core Data - Create NSManagedObject Subclass
I created a test app called Template9b1. The first step I've taken is to use a Template Master / Detail with Core Data. I modified the Entity (called Event) with 4 properties instead of the default timestamp. I used Create NSManagedObject Subclass, and it created the 2 files as it should.// Event+CoreDataProperties.swiftimport Foundationimport CoreDataextension Event { @NSManaged var theDate: NSDate? @NSManaged var name: String? @NSManaged var favorite: String? @NSManaged var status: NSNumber?}// Event.swiftimport Foundationimport CoreData@objc(Event)class Event: NSManagedObject { // Insert code here to add functionality to your managed object subclass}When I run it (simulator), I get an error2015-06-16 23:34:48.842 Template9b1[50760:1014766] CoreData: warning: Unable to load class named 'Template9b1.Event' for entity 'Event'. Class not found, using default NSManagedObject instead.In the past, to get rid of this type of error, I would put the name of the app Template9b1 in the module for the inspector of the
5
0
6.9k
Jun ’15
Reply to GameplayKit - how do you set up GKLinearCongruentialRandomSource
Okay - I think I have identified what the actual issue is. Playgrounds inherently hide the 'debug' area so I did not see the error code that was being generated.Here is the error:Playground execution failed: /var/folders/_9/sqdvh1m923j0ts4t7sldpyvr0000gn/T/./lldb/10162/playground861.swift:22:14: error: 'GKLinearCongruentialRandomSource' is only available on iOS 9.0 or newer let random = GKLinearCongruentialRandomSource(seed: seed) ^ /var/folders/_9/sqdvh1m923j0ts4t7sldpyvr0000gn/T/./lldb/10162/playground861.swift:22:14: note: guard with version check let random = GKLinearCongruentialRandomSource(seed: seed)So the real issue is my Xcode 7 beta playground does not appear to be recognized as IOS 9. Is there a way to set Playground's IOS level? I have verified in the File Inspecter that this playground is IOS and not OS X - but I can't find a way to change the IOS version.
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
Reply to Exhaustive catch inference
I can't think of a reason to believe the compiler can ever infer exhaustiveness of implementations of ErrorType. It might be able to do so as far as your module is concerned, but surely there's always the possibility of errors from other modules, and from the runtime itself.So it seems to me that at best the absence of 'catch {…}' could compile to a run-time check that the actual error hasn't failed to match the catches you supply. In effect, this would be a compiler-supplied catch-all-crash. (In a throwing function, this would be a compiler-supplied catch-all-rethrow.) But it seems to be against Swift's design principles to crash at places where you haven't said it could (where you haven't coded a !).
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’15