Xcode 3 would show me the line that caused a crash when debugging.
How do you turn this feature on in Xcode 4 ??
I have added an Exception Breakpoint as suggested here but no joy:
How to display the exact line of code causing application crash in xcode 4 debugger like in xcode 3.2
Related
I'm trying to start a new Xcode project in the beta 4 with the game template but I can't get rid of the "Hello" label because it seems to be hidden in one of the .sks files.
Problem: Xcode 8 will crash every single time I try to open an .sks file.
Any solution to this, other than waiting for the next beta?
Thanks for your help.
Running the simplest, default code in Xcode 7 playgrounds... get the following error
Playground execution failed: Execution was interrupted, reason: EXC_BAD_ACCESS (code=1, address=0x8).
* thread #1: tid = 0x351bc3, 0x00000001062019ca libicucore.A.dylib`utext_clone + 22, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8)
* frame #0: 0x00000001062019ca libicucore.A.dylib`utext_clone + 22
frame #1: 0x000000010633ac42 libicucore.A.dylib`icu::RegexMatcher::reset(UText*) + 54
frame #2: 0x0000000106375414 libicucore.A.dylib`uregex_setText + 222
frame #3: 0x0000000103d1b445 Foundation`-[NSRegularExpression(NSMatching) enumerateMatchesInString:options:range:usingBlock:] + 2325
frame #4: 0x0000000103d65d7e Foundation...
Cannot run anything in playgrounds basically.
Running beta 4 (7A165t)
I also have Xcode 6.2 running playgrounds just fine on the same mac.
Complete reinstall of all versions of Xcode plus deleting folder Library/Developer fixes the issues (see https://forums.developer.apple.com/thread/13969).
I just had this issue - before a fresh install check you haven't got IOS simulator running in the background anywhere from another xcode project or previous session. Once I closed the IOS simulator, closed xcode and re-launched and opened the playground again it worked fine. Seems I had a problem with xcode trying to open multiple simulators.
EXC_BAD_ACCESS Exception thrown when you try to send a message to already released object.
Apple provides mechanics with special class NSZombie which replace every released object in memory.
You could find more details on following links:
http://www.touch-code-magazine.com/how-to-debug-exc_bad_access/
http://loufranco.com/blog/understanding-exc_bad_access
I've just upgraded to XCode 6 (iOS 8 SDK) and I am getting the following warning and error in the console that did not occur in XCode 5 (iOS 7 SDK):
2014-06-08 08:58:57.266 ColorChaos[3250:138871] SetAppThreadPriority: setpriority failed with error 45
2014-06-08 08:59:27.303 ColorChaos[3250:138871] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSSetM addObject:]: object cannot be nil'
The SetAppThreadPriority seems to be just a warning because the app continues to run, but a few seconds/touches in it crashes with the NSInvalidArgumentException error.
Has anyone else experienced anything similar after updating? The error is not occurring in my code (I don't think), it highlights the line in main.m with Thread 1: signal SIGABRT.
Thanks in advance.
EDIT: I should note I've just realised XCode 5 is still installed along side XCode 6 and I can still compile and run my code in that so it's not really an issue any more but it would still be nice to know if it can be fixed.
I was running into a similar problem. If you're running off an iOS simulator make sure it's set to iPhone 5 or above. Swift code won't run on iOS 4 which, I believe, is the default emulator device for XCode 6.
I am trying to run my app for IPhone in xcode 4.2 and it keeps shutting down. From what I've heard, SIGABRT can come from many places. I have tried restarting the computer and resetting the iOS simulator already. The build succeeds, but then pops out this error before I can test the app. The error is in the main.m file.
0x00001fa8 <+0152> mov -0x38(%ebp),%ecx
Thread 1: Program received signal: "SIGABRT"
SIGABRT means that there was an error thrown somewhere in your code. This could happen due to a wide range of problems. Try setting an exception breakpoint in the breakpoint navigator or manually set breakpoints yourself to see where the exception was thrown. Also you can look in the debugger console to see where the exception came from.
Apparently out of nowhere I've suddenly started getting a compilation error, which only occurs when building for the simulator:
Command /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool failed with exit code 255
It compiled this morning, I have not changed the xib, now this afternoon it fails.
What is it and why is it only for the simulator?
EDIT - the number of errors increasing, first it was one, then I relaunched x code, then it was two, now its increased to 3.
EDIT - Now XCode crashes whenever I try to view any xib.
Maybe time for a reinstall
I had a similar error once. In my case I had edited the SourceCode of a storyboard and failed to add a file in the section.