crash-reports

问题 I've been receiving a few crash logs for a bug that I haven't been able to replicate. The crash occurs right when the user taps on a textView in the app. The textView is located under a tableView and I extend the bottom constraint of the textView to fit the keyboard on screen. The constraint extends through keyboard notifications (NSNotificationCenter keyboardWillShow). Below are two crash logs. Any help would be appreciated! Exception Type: EXC_CRASH (SIGABRT) Exception Codes:

问题 I am building a cross-platform mobile app in HTML, CSS & Javascript and publishing it to Android and iOS using PhoneGap as a wrapper. I have published in the Android Market, and am finding out through customer reviews that the app stalls early during the user setup phase, with some users/devices. I do not have any kind of error handling and reporting set up in the app, and the Android Market's crash report is still giving me 0 crashes after hundreds of downloads and half a dozen disappointed

问题 I'm investigating a JVM crash on one of our production systems, what do the following memory values represent in the hs_err_pid log file snippet below? Heap par new generation total 1258624K, used 955445K [0x00000005c0000000, 0x00000006155b0000, 0x000000066aaa0000) eden space 1118784K, 73% used [0x00000005c0000000, 0x00000005f1e52598, 0x0000000604490000) from space 139840K, 98% used [0x000000060cd20000, 0x00000006153db100, 0x00000006155b0000) to space 139840K, 0% used [0x0000000604490000,

问题 We got a .NET WCF service that should be 100% uptime ideally. But sometimes we have a memory leaking issues in our application that caused by 3rd party DB connectivity component. We configured nnCron to watch for process existence and when the process of that service is exited, it should start it again. But when the app is crashing down windows pops up an noisy window informing that app has crashed. Here it is: And only when we click on dumb "Close the program" button, the process really

问题 I got (in ITC) below presented crash report for my first Mac App Store app. Using knowledge founded on Stackoverflow I tried to symbolicate this log, but (using atos and otool) I was only able to read last (20) line (which means start (in My App) + 52 . I really don't know how to interpret lines above, and how to find cause of crash. Process: My App [270] Identifier: com.mycompany.myapp Version: 1.0.0 (1.0.0) App Item ID: 568750000 App External ID: 11410000 Code Type: X86-64 (Native) Parent

问题 I need to symbolicate some crash logs and for that I read that I need the .app and the .dSYM files together with the .crash files. I can't find the .app file anywhere. I have the .app.dSYM file and the .crash ones but I can't find the .app one. I can also see my error logs on the Xcode Organizer. But the lines from my Application are not symbolicated. And if I click on the arrow to open with a project, I have no idea which file to open. Thanks 回答1: When you build your iOS project, you should

问题 I have an C++ application, that crashes on a computer of some person on the other end of the world. There's no way for me to simulate it or get the same computer. The person is no developer, so I cannot really ask him to install Visual Studio or something. I have pretty deep debug logs, but they didn't reveal anything usable. Is there a tool, that could generate the stack trace of the application at the moment of the crash? Such thing is available inside OSX, but seems that Windows doesn't

问题 I've been following this tutorial on how to enable Parse Crash Reporting: https://www.youtube.com/watch?v=L4SMyHAVJgk However, after I create the run script and build my app, I get the following error: /bin/sh failed with exit code 2 I'm not the best at understanding weird error codes like this so any help would be greatly appreciated! Here is my run script: export PATH=/usr/local/bin:$PATH cd </Users/dom/MyApp/parse> parse symbols "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}" Also, I'm

问题 I got several crash reports in x-code(reported by users) but unable to find out what is it for. I opened it in project but it doesn't show me code line where crash occurred (obviously i tried clicking on every line of the stack trace). 回答1: If you want to trigger Crashes in your released builds so you should integrate crash reporter in your project and Crashlytics is one of them. Integrate Crashlytics Integrate it and release your build to client or tester. Whenever it will crash you will be

问题 I have just started working on a Windows Store App written in C#, it has not yet been published to the Windows Store. When I give a debug build of the app being developed to my testing team and it crashes where can they find the crash log and stack trace? Do I need to do anything when building my application? I'm looking for the standard solution, not a third party library or something that sends me reports from end-users. I'm coming from an Android world where the ADB logcat always contains