sigabrt

Swift 3 - SIGABRT error - numberOfComponentsInPickerView:]: unrecognised selector sent to instance

久未见 提交于 2020-03-03 09:23:27
问题 Just updated to Swift 3 and xCode 8 Beta 4. After fixing all the code issues I now have an error free project but it is throwing a SIGABRT error when clicking one particular button on my front screen. I am sure that it is something to do with the UIPickerView element on the destination page as I have deleted, checked and re added all segues and outlets to make sure everything is clear from that side. The console is showing the following: 2016-08-02 18:59:46.607 ForceIt![38735:2895259] -

NSMutableDIctionary setObject: ForKey crashing when Key is member of Object

别来无恙 提交于 2020-01-26 01:52:57
问题 I'm trying to use an NSMutableDictionary to pair my custom classes object with a UIButton as it's key. The UIButton that is the key is also a member of the object that I want to store as the object in the NSMutableDictionary. My Class definition looks like ths: @interface ClassA : NSObject { @public UIButton *button1; UIButton *button2; UILabel *label; } @property (nonatomic, retain) UIButton *button1; @property (nonatomic, retain) UIButton *button2; @property (nonatomic, retain) UILabel

addObject for NSMutableArray crashes!

北慕城南 提交于 2020-01-16 12:34:07
问题 I am dealing with a problem which is driving me mad. I have looked at other forums and my code seems to be ok, however it fails when invoking addObject method for NSMutableArray. I am implementing a simple xml parser class and storing some of the information in a NSMutableArray: - (void)parser:(NSXMLParser *)parser didEndElement:(NSString *)elementName namespaceURI:(NSString *)namespaceURI qualifiedName:(NSString *)qName{ if([elementName isEqualToString:@"Image"]){ [images setObject: [

addObject for NSMutableArray crashes!

假装没事ソ 提交于 2020-01-16 12:34:03
问题 I am dealing with a problem which is driving me mad. I have looked at other forums and my code seems to be ok, however it fails when invoking addObject method for NSMutableArray. I am implementing a simple xml parser class and storing some of the information in a NSMutableArray: - (void)parser:(NSXMLParser *)parser didEndElement:(NSString *)elementName namespaceURI:(NSString *)namespaceURI qualifiedName:(NSString *)qName{ if([elementName isEqualToString:@"Image"]){ [images setObject: [

WebView in NestedScrollView gives Fatal signal 6 (SIGABRT) code -6 RenderThread

时光总嘲笑我的痴心妄想 提交于 2020-01-16 03:01:09
问题 I have an activity with a ViewPager and TabLayout as below: <?xml version="1.0" encoding="utf-8"?> <android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent" xmlns:app="http://schemas.android.com/apk/res-auto"> <android.support.design.widget.AppBarLayout android:id="@+id/item_appbar" android:layout_width="match_parent" android:layout_height="wrap_content"> <android.support

Vector and deque initialization or push_back causes SIGABRT error

不想你离开。 提交于 2020-01-15 05:08:06
问题 I'm getting a weird error, when initializing my deque or vector. I'm using QtCreator and a CMake-Project. If I use a deque, it aborts on initialization: std::deque<int> myValues; // <-- abort here for (int i=0;i<10;++i) { myValues.push_back(i); } when I use deque, it aborts on push_back: std::vector<int> myValues; for (int i=0;i<10;++i) { myValues.push_back(i); // <-- abort here } I can't find out why this is happening now (it worked that way all the time). Both aborts happen inside _gnu_cxx:

Turning on Thread Sanitizer results in signal SIGABRT

久未见 提交于 2020-01-13 04:52:12
问题 When I create a new Single View App from in Xcode Version 11.3 (11C29) and run it all is ok. When I turn on Thread Sanitize And try to run the very same app, I get Thread 1: signal SIGABRT this is the backtrace (lldb) bt * thread #1, stop reason = signal SIGABRT * frame #0: 0x00007fff523d5bea libsystem_kernel.dylib`__abort_with_payload + 10 frame #1: 0x00007fff523d74f3 libsystem_kernel.dylib`abort_with_payload_wrapper_internal + 80 frame #2: 0x00007fff523d74a3 libsystem_kernel.dylib`abort

NSInvalidArgumentException when deleting cell using a different class

扶醉桌前 提交于 2020-01-07 02:35:11
问题 Update for code: Following on Matthew's answer I tried correcting my code to be more correct. Now the code does delete the cell but also crashes and gives an error: * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[__NSPlaceholderArray initWithObjects:count:]: attempt to insert nil object from objects[0]' The code below is from an action called checkboxTapped which is in my CustomCell code. Once action is fired it gives the error. I figured out that my

iOS App Crash On Launch With Only LLDB() (The App Works In Simulator)

血红的双手。 提交于 2020-01-05 07:08:48
问题 Just finished updating codebase to Swift 4. It is working fine in the simulator. When I build to a device I get an instant crash with no error message: It works fine in the simulator. There are some threads on it: App crashes only with (lldb)? iOS app crashes with no error, just (lldb) dyld`__abort_with_payload: With no error message From what I learned the problem might be linked binaries but I've dug into my linked binaries and I believe everything is linked correctly. Any thoughts on where

NSArray: Why is SIGABRT sent instead of an 'index out of bounds' kind of error?

 ̄綄美尐妖づ 提交于 2020-01-05 01:36:31
问题 Ok. So I had this extremely weird SIGABRT error on a complex Objective-C iOS program that I'm working on, and after one day of tracking I found the culprit. Let's say we have the following code: NSArray *a = [NSArray arrayWithObjects:@"a", @"b", @"c", nil]; NSLog(@"tada: %@", [a objectAtIndex:-1]); Why the hell will this terminate the program with Program received signal: SIGABRT and the debugger not even pointing to my code (but rather in some assembly part) instead of a nicer 'index out of