bitstadium / crashprobe Goto Github PK

Could be interesting to see how Parse performs: http://blog.parse.com/2014/12/09/introducing-parse-crash-reporting-2/

The following crashes result in perfectly fine crash logs for me where as the website states they do not:

– Objective-C Exception (ARM64)
– Released Object (ARM64)
– Bad Pointer (ARM64)

I notice that CrashProbe.com overview section shows there are 44 cases . But when I check the git repo, there are only 22 case in the project.

Is it because you regard different architecture (ARMv7 and ARM64) as two different condition so double the cases?

Since everybody has to redo their tests now (#6), can we also discuss the result of the Swift test (probably in another issue)?

Referencing the previous discussion between @anlinde @mitsuhiko bitstadium/CrashProbe-Data#15 (comment)
https://github.com/bitstadium/CrashProbe-Data/blob/master/ios/22/_sentry_arm64.crash#L12

Just wanted to get the opinion of other contributors about the issue, since we still think our result is not incomplete it shows more information. The result that we propose is matching what lldb/xcode and other systems do (eg: show inlined frame information).

The website for this repo crash http://crashprobe.com/ returns 404 from Github Pages.

Thanks for giving us a way to test crash reporters.

It's would be interesting to see how KSCrash performs.

Is the CrashProbe site updated with the last version of HockeyApp which use PLCrashReporter 1.2 ?

Xcode 11 does not support Swift 3 any more

The data hosted on the CrashProbe site is now wildly out-of-date with the latest versions of these analytics packages. For example, the Crashlytics tested at the time of the last run was version 3.4.1 from November 19, 2015 where the latest is 3.8.4 from February 22, 2017. Please update the results.