sigabrt

C++: vector<string> *args = new vector<string>(); causes SIGABRT

纵然是瞬间 提交于 2019-11-28 08:54:52
问题 Pretty self explanatory. Here's the method that's causing the SIGABRT on the 'new vector' line: vector<string> * Task::arguments() { vector<string> *args = new vector<string>(); // CAUSES SIGABRT int count = sizeof(_arguments); for (int x = 0; x < count; x++) { string argument(_arguments[x]); args->push_back(argument); } return args; } Note that elsewhere I call that exact line without any issues. Here is the list of includes in the Task class: #include <vector> #include <unistd.h> #include

iOS app crashing every other launch, can't find error

给你一囗甜甜゛ 提交于 2019-11-28 03:26:04
First time I launch the app, everything seems to run fine. I'll hit the stop button, do some work and when I go to launch it again, it seems to crash before it can even load anything. Press stop, hit Run again, and it works fine. Until I repeat the process. This is where xcode is highlighting the error with "Thread 1:signal SIGABRT". Obviously nothing useful here. int main(int argc, char *argv[]) { @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([PokerAppDelegate class])); } } The debug console shows nothing besides (lldb) (So I suppose its stopping, not crashing

How to read crash log? How to find why the app crashes in system library? What means EXC_CRASH (SIGABRT)?

老子叫甜甜 提交于 2019-11-28 00:50:37
问题 I got an crash logs from a customer to figure why my app crash on her iPhone. Here some info from crash log: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x00000000, 0x00000000 Crashed Thread: 0 Stack trace for Thread 0 Thread 0 Crashed: 0 libSystem.B.dylib 0x3293f98c 0x328c1000 + 518540 1 libSystem.B.dylib 0x3293f97c 0x328c1000 + 518524 2 libSystem.B.dylib 0x3293f96e 0x328c1000 + 518510 3 libSystem.B.dylib 0x3295461a 0x328c1000 + 603674 4 libstdc++.6.dylib 0x30a143b0 0x309cf000 +

Xcode 4.2 SIGABRT Error

天大地大妈咪最大 提交于 2019-11-27 09:06:15
Everytime I run my app on the iPad simulator, it works flawlessly. But, when I run it on the iPhone simulator, when I click the home button, I get an error in Xcode in my main.m file, saying "Thread 1: Program received signal: SIGABRT". It is highlighting this line in my main.m's code: return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); This issue doesn't occur when I press the home button on the iPad simulator at all though. I've done a lot of research on here about this error, but nothing useful seemed to turn up. Does anyone know how to go about fixing this?

iOS app crashing every other launch, can't find error

一个人想着一个人 提交于 2019-11-27 05:11:09
问题 First time I launch the app, everything seems to run fine. I'll hit the stop button, do some work and when I go to launch it again, it seems to crash before it can even load anything. Press stop, hit Run again, and it works fine. Until I repeat the process. This is where xcode is highlighting the error with "Thread 1:signal SIGABRT". Obviously nothing useful here. int main(int argc, char *argv[]) { @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass(

Android app crashes with SIGABRT Signal 6 only while Eclipse debugging

て烟熏妆下的殇ゞ 提交于 2019-11-26 22:18:52
I have an app that runs perfectly fine on a device without a debugger attached. However, I have a problem when debugging in Eclipse: When the main thread is suspended for about 10 seconds or more (for example after hitting a breakpoint), the main thread throws a SIGABRT, apparently coming from libc. The only explanation I could think of is that the message queue on the main thread, when not being polled, is overflowing with messages coming from another thread. However, I don't see the heap growing when the main thread is suspended. Moreover, while my app has about 20 threads between all

How to track down cause of SIGABRT

旧街凉风 提交于 2019-11-26 18:41:47
I'm showing the code to this problem for example purposes, but really my question is: how am I supposed to track down and understand SIGABRT errors? I read this question: sigabrt with no error message , however I don't think this pertains to my problem. The example I'll show below is obviously not a xib problem, and prior times getting SIGABRT seemed more to do with unhandled exceptions. I have tried using GDB's bt but this does not help. Is there not a more comprehensive dump to view? I have also used NSZombie , but I really don't understand how to use it, so if that is your answer, please

Xcode 4.2 SIGABRT Error

走远了吗. 提交于 2019-11-26 14:29:50
问题 Everytime I run my app on the iPad simulator, it works flawlessly. But, when I run it on the iPhone simulator, when I click the home button, I get an error in Xcode in my main.m file, saying "Thread 1: Program received signal: SIGABRT". It is highlighting this line in my main.m's code: return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); This issue doesn't occur when I press the home button on the iPad simulator at all though. I've done a lot of research on here

Exception Type: EXC_CRASH (SIGABRT)

匆匆过客 提交于 2019-11-26 11:26:39
问题 Incident Identifier: B959CD08-FA2C-4A34-8D0C-343927FF6B86 CrashReporter Key: 78e6625f679cb4cfb76f553075c64a197002c1bf Hardware Model: iPad3,1 Process: ktv [50343] Path: /var/mobile/Applications/B8971D06-6001-49F7-81E1-8B88CDA5EB03/ktv.app/ktv Identifier: ktv Version: ??? (???) Code Type: ARM (Native) Parent Process: launchd [1] Date/Time: 2013-01-09 18:59:32.193 +0800 OS Version: iPhone OS 5.1.1 (9B206) Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x00000000,

Android app crashes with SIGABRT Signal 6 only while Eclipse debugging

巧了我就是萌 提交于 2019-11-26 08:14:08
问题 I have an app that runs perfectly fine on a device without a debugger attached. However, I have a problem when debugging in Eclipse: When the main thread is suspended for about 10 seconds or more (for example after hitting a breakpoint), the main thread throws a SIGABRT, apparently coming from libc. The only explanation I could think of is that the message queue on the main thread, when not being polled, is overflowing with messages coming from another thread. However, I don\'t see the heap