Search results for

LLDB crash

29,559 results found

Post

Replies

Boosts

Views

Activity

Reply to GuidedTour.playground not opening in Xcode 6.3.2
The version from the old 1.2 Swift book works for me in Xcode 6.3.2, but the version linked to from the current (prerelease) Swift 2 book appears to be corrupted and missing files inside the playground package.GuidedTour.playground for Swift 1.2 (works for me w/ Xcode Version 6.3.2 (6D2105) on OS X 10.10.3, modification date 2015-06-05)https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.playground.zipIt opens properly in Xcode 7 beta as well, it just has errors due to the changes between Swift 1.2 and Swift 2.GuidedTour.playground for Swift 2 (crashes Xcode 7 beta 2 (7A121l) on OS X 10.10.3, modification date 2015-06-22)https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.playground.zip(linked to from https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html#//apple_ref/doc/uid/TP40014097-CH2-ID1)If you open the
Jun ’15
fatal error: call of removed method
Hi,Does anyone have any clue about this error message?fatal error: call of removed methodI am getting this crash from Xcode after trying to use a Class function from a custom framework made in Swift.Setup is as followpublic protocol Something { var prop1: String { get } var prop2: [String] { get } var prop3: [String] { get } ... } public class Things { public class func stuffWithName(name: String) throws -> Something { return try Stuff(name: name) } } struct Stuff: Something { let prop1: String let prop2: [String] let prop3: [String] init(name: String) throws { ...do stuff... } }Things.stuffWithName(Sockets)This works perfectly in Unit Testing but crash when the framework is used within an App.The weirdest is that I have other objects using the exact same architecture and they don't crash.Any clues where I could dig further?Cheers
3
0
5k
Jun ’15
crash during initalization in CGFontCreateFontsWithPath
Just updated app w/ Xcode 7, getting a crash on initialization in UIApplicationMain, seemingly due to fonts.(I noticed that Xcode 7 put a customFonts entry in my main .xib file .. maybe related?)+ <customFonts key=customFonts> + <mutableArray key=Helvetica.ttc> + <string>Helvetica</string> + <string>Helvetica</string> + <string>Helvetica</string> + <string>Helvetica-Bold</string> + <string>Helvetica-Bold</string> + <string>Helvetica-Bold</string> + <string>Helvetica-Bold</string> + <string>Helvetica</string> + </mutableArray> + </customFonts>* thread #1: tid = 0x9f65, 0x000000010dc11c6b libc++abi.dylib`__cxa_throw, queue = 'com.apple.main-thread', stop reason = breakpoint 1.2 frame #0: 0x000000010dc11c6b libc++abi.dylib`__cxa_throw frame #1: 0x00000001106127c8 libFontParser.dylib`TFileDescriptorContext::TFileDescriptorContext(char const*) + 142 frame #2: 0x00000001106125d0 libFontPa
3
0
2.7k
Jun ’15
Reply to crash during initalization in CGFontCreateFontsWithPath
This is the debugger hitting a breakpoint, not a crash. You have presumably set a breakpoint on all exceptions, including for C++ (as opposed to just Objective-C). The thing is, unlike Objective-C, exceptions are sometimes used in normal situations by C++ code. They don't necessarily indicate an unrecoverable error or impending crash.In general, unless you're debugging C++ code and specifically interested in the exceptions thrown by it, you should set your breakpoint to just stop on Objective-C exceptions. Ignore the C++ exceptions. They will most likely be caught and handled by the C++ code and not actually cause any problem.
Jun ’15
Reply to Does anyone know the Metal system requirements?
Well, I finally got around to installing the OS X 10.11 and Xcode 7 betas on my 2008 Mac Pro (which has a PC GTX 760 card), and the MetalKitEssentials sample code compiles and runs just fine. So thankfully Metal seems to rely on the actual video card, rather than some motherboard feature or an artificial cutoff.I haven't tried it on my 2008 Macbook Pro, yet, but since I can't upgrade that video card, I doubt it'll do anything. I wonder what the behavior is when you try to run it on unsupported hardware?Update: Yep, crashed at runtime on my 2008 MBP... The log says that newRenderPipelineStateWithDescriptor failed, which was then used to create a (presumably) invalid MTKMeshBufferAllocator, which then caused [[MDLAsset alloc] initWithStuff] to throw an exc_bad_access error.
Topic: Graphics & Games SubTopic: General Tags:
Jun ’15
Debug SIGTERM handler in Xcode?
Xcode 6.3.2I have a daemon that hooks SIGHUP, SIGINT, and SIGTERM. They all direct the signals to call a signal_handler() function.I was having an intermittent crash when the daemon was existing, so I ran the process in Xcode hoping to catch the problem. Unfortunately, I can't reproduce it. When I send the process a SIGTERM (kill -TERM <pid>), Xcode breaks in my run loop and says my process received a SIGTERM. Unexpected, but OK.But then I click on the Continue button and ... nothing happens. The program goes right back to running normally, The signal_handler() function is never called.Does anyone know how I can debug signals using the debugger, without the debugger intercepting it and eating the signal?
4
0
9.5k
Jun ’15
Reply to Debug SIGTERM handler in Xcode?
You need to use the process signal SIGTERM command at the lldb console prompt to continue and deliver the signal.Alternatively, you can use process handle -s0 -p1 SIGTERM in advance to tell the debugger to not stop when the signal is received and to pass it along to the debugee.
Jun ’15
Reply to Swift 2 dictionary extension for a property list, how to?
This is helpful, and your suggestion is encouraging me to lean towards a non-pure solution, so thank you for that 🙂. Unfortunately, the code above crashes in my use case (feeding it a dictionary read from a property list file), and it still has some of the problems I'm seeking to avoid, namely, the as! Key cast, and frequent use of NS objects, however I think I'm ready to give up the ghost on the latter.I should have been clearer about the code that works, but feels wrong, it was this:extension Dictionary { func hasIntroduction() -> Bool { if let value = self[kHasIntroductionKey as! Key] as? NSString { return value.boolValue } return false } }The following alternative extension, on NSDictionary, eliminates the as! Key conversion, and is what I am currently leaning towards:extension NSDictionary { func hasIntroduction() -> Bool { if let value = self[kHasIntroductionKey] as? NSString { return value.boolValue } return false } }I'm still holding out hope that there is a more general Swift solution
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’15
This application is modifying the autolayout engine from a background thread
I am working with iOS 9 and Xcode 7. My app crashes when I build and run it. I get the following error. I have no idea how I am modifying the autolayout engine on a background thread. I may not be providing all of the neccessary info but I am not sure what someone would need to see in order to help solve the issue.I do know that this is called six times and I do have six of the same type of view controller. This application is modifying the autolayout engine from a background thread, which can lead to engine corruption and weird crashes. This will cause an exception in a future release. Stack:( 0 CoreFoundation 0x000000010fb8bca5 __exceptionPreprocess + 165 1 libobjc.A.dylib 0x000000010f604dcd objc_exception_throw + 48 2 CoreFoundation 0x000000010fb8bbdd +[NSException raise:format:] + 205 3 Foundation 0x000000010f37f7cf _AssertAutolayoutOnMainThreadOnly + 79 4 Foundation 0x000000010f1e227e -[NSISEngine withBehaviors:performModifications:] + 31 5 UIKit 0x000000011098a304 -[UIView(AdditionalLa
Topic: UI Frameworks SubTopic: UIKit Tags:
11
0
22k
Jun ’15