crash-reports

iOS: How to get stack trace of an unhandled std::exception?

前提是你 提交于 2019-11-30 01:28:23
问题 If an unhandled NSException is thrown, the stack trace has a section like this: Last Exception Backtrace: 0 CoreFoundation 0x32bd688f __exceptionPreprocess + 163 1 libobjc.A.dylib 0x34b7b259 objc_exception_throw + 33 2 CoreFoundation 0x32bd65c5 -[NSException init] + 1 3 Foundation 0x37296bd7 -[NSObject(NSKeyValueCoding) valueForUndefinedKey:] + 263 ... But if std::exception is thrown, i get only this: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x34f2632c __pthread_kill + 8 1 libsystem_c.dylib

EXC_BAD_ACCESS in UIWebView

自作多情 提交于 2019-11-29 20:18:52
I just downloaded the crash reports for one of my iPhone apps from iTunes Connect. The most common crash has a trace like the following: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0xa1b1c1db Crashed Thread: 0 Thread 0 Crashed: 0 libobjc.A.dylib 0x3030e6f4 objc_msgSend + 16 1 UIKit 0x30ebebee -[UIWebView webView:resource:didFinishLoadingFromDataSource:] 2 UIKit 0x30ebe5ca -[UIWebViewWebViewDelegate webView:resource:didFinishLoadingFromDataSource:] 3 CoreFoundation 0x32b73b5c __invoking___ + 60 4 CoreFoundation 0x32bc67be -[NSInvocation invoke] 5 WebCore

Crash logs generated by iPhone Simulator?

天大地大妈咪最大 提交于 2019-11-29 19:30:06
Are there any crash logs generated by iPhone Simulator? the Simulator crashes a lot but not leaving any traces in Console... the crash log will be useful. ohhorob The console will show the NSLog() output from an app running in the simulator. The crash logs are saved to file. I have found some in my home directory under ~/Library/Logs/DiagnosticReports/ They have a file extension of .crash Something I haven't yet figured out is how to get them to generate even if the debugger grabs the EXC_BAD_ACCESS signal. Update Currently, (OSX 10.11.6), the .crash logs in ~/Library/Logs/DiagnosticReports ,

How to locate app crash logs in iPhone & iPad?

允我心安 提交于 2019-11-29 19:21:05
问题 If any iOS app crashes some crash logs are generated on behalf of that app. How to find the location of such crash logs. Please help. I want crash logs inside the iPhone/iPad, not really using XCode to see the crash logs. 回答1: I think he/she asked about crash logs inside the iPhone/iPad, not really using XCode to see the crash logs. To check the crash logs inside iPhone/iPad, you have to go to Settings -> General -> About -> Diagnostics & Usage -> Diagnostic & Usage Data You will see the

how can I send log information from my Android app to my server?

微笑、不失礼 提交于 2019-11-29 18:44:29
问题 I'm developing an Android app that is currently in the Play Store. I've been getting reports of a crash on certain devices that I can't reproduce, and the Play Store's built in crash diagnostics don't contain enough information. What I really need is the Logcat information from these devices, but it seems that Android 4.1 and above don't allow the use of those "Log Collector" apps that used to be so popular for this purpose due to security concerns. Is there a library that I can add to my app

Springboard crashing when adding a lot of triggers to UNUserNotificationCenter

半腔热情 提交于 2019-11-29 15:21:01
问题 Save yourselves from hours of debugging, because I've just wasted 2 weeks after bug hunting mysterious app crashes. It turns out, if you're adding a lot o (see answer for more details) notification requests to the UNUserNotificationCenter , it will abruptly crash the Springboard. I haven't found a way around this yet, as the same code worked fine for iOS 9 and below. You can't seem to bulk-add notification requests like before either. Following is the crash I receive every single time (and so

SIGSEGV SEGV_ACCERR Crash Reports - What to do?

旧时模样 提交于 2019-11-29 11:26:40
问题 I've just released an app on the AppStore with Crittercism crash reporting and I've been getting quite a few crash reports pertaining to a SIGSEGV error. Crittercism gives me a StackTrace and a few handy details about usage statistics, etc. however, I'm still befuddled by these symbolized stack traces. I have a few questions in general about this kind of thing - Many of the classes and methods in the Stack Trace are not even used in my app (to my knowledge), which leads me to believe that

How do you interpret a deobfuscated Android crash report?

依然范特西╮ 提交于 2019-11-29 04:51:22
I downloaded a crash report from my app's Google Play admin area, ran it through retrace.sh to deobfuscate the Proguard mapping, and it produced the output below. Questions: What is Unknown Source? showHeader , showPhoto , etc. are indeed methods in my SummaryFragment class, but why are they listed in the order shown? These methods do not follow any sort of logical or execution order in my code. In which method was the NPE actually thrown? Caused by: java.lang.NullPointerException at com.myapp.SummaryFragment.selectMenuItemAuth(Unknown Source) showHeader photoButtonClicked showPhoto

how to understand Crash Log of iPhone

假装没事ソ 提交于 2019-11-29 03:52:37
i only know it Crash not run out of memory. how did i know which it cause of error? Incident Identifier: 242C320A-763C-407E-BD40-443E3E9B611C CrashReporter Key: 307097bc0924dac79e5352eb10692943c0ef05ad Process: AsianDelight [4894] Path: /var/mobile/Applications/7A8FF881-A033-45B9-8F72-8478217821E9/AsianDelight.app/AsianDelight Identifier: AsianDelight Version: ??? (???) Code Type: ARM (Native) Parent Process: launchd [1] Date/Time: 2010-01-20 16:32:49.285 +0700 OS Version: iPhone OS 3.1.2 (7D11) Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION

ios:EXC_BAD_ACCESS for Webview delegate

泪湿孤枕 提交于 2019-11-29 02:26:12
I have a situation where I am trying to resolve these Crashlytics issues and I have this crash log Thread : Crashed: com.apple.main-thread 0 libobjc.A.dylib 0x34217f46 objc_msgSend + 5 1 UIKit 0x29a2d5a3 -[UIWebView webView:decidePolicyForNavigationAction:request:frame:decisionListener:] + 182 2 CoreFoundation 0x2630cad4 __invoking___ + 68 3 CoreFoundation 0x26239645 -[NSInvocation invoke] + 300 4 CoreFoundation 0x2623d0c7 -[NSInvocation invokeWithTarget:] + 50 5 WebKitLegacy 0x326d9261 -[_WebSafeForwarder forwardInvocation:] + 224 6 CoreFoundation 0x2630b62f ___forwarding___ + 354 7