Reliable, open-source crash reporting for iOS, macOS and tvOS
Перейти к файлу
Ivan Matkov 854d20f74e TEMP remove apple silicon from CI 2020-11-06 11:23:47 +03:00
.azure-pipelines TEMP remove apple silicon from CI 2020-11-06 11:23:47 +03:00
.github Add GitHub templates 2020-07-03 14:51:39 +03:00
CrashReporter.xcodeproj Bump version to 1.8.1 2020-11-06 11:02:33 +03:00
Dependencies Add CG manifest for protobuf-c 2020-04-28 11:09:27 +03:00
Documentation/Crash Log Format Rename to 'Crash Log Format' 2008-12-16 07:31:54 +00:00
Other Sources Fix macOS framework settings 2020-06-25 15:02:32 +03:00
Resources Fix macOS framework settings 2020-06-25 15:02:32 +03:00
Scripts Fix typos 2020-10-21 15:32:42 +03:00
Source Merge branch 'master' into min-ios-9 2020-10-16 14:42:49 +03:00
Tests Fix unit test 2020-10-14 14:04:43 +03:00
Tools/CrashViewer Merge branch '1.2-with-master' into prepre-for-merge 2019-10-18 17:52:26 +03:00
include Add SPM support 2020-04-30 19:09:26 +03:00
.gitignore Update autogenerated files and ignore temp file that produced by doxygen 2020-04-29 20:15:36 +03:00
CHANGELOG.md Update changelog 2020-11-06 11:09:37 +03:00
Doxyfile update doxyfile, fix unbalanced grouping commands 2020-05-08 19:34:33 +04:00
LICENSE Add MS copyright 2020-03-06 10:12:59 -08:00
PLCrashReporter.podspec Bump version to 1.8.1 2020-11-06 11:02:33 +03:00
Package.swift Drop support of iOS 8. The minimal version is iOS 9 now 2020-10-09 16:59:44 +03:00
README.md Merge branch 'master' into v-ivmatk/apple-silicon-ci 2020-10-19 15:29:19 +03:00
ThirdPartyNotices.txt Remove "Catch" from 3rd party notices 2019-10-18 17:04:14 +03:00

README.md

CocoaPods Carthage compatible SwiftPM compatible

PLCrashReporter

PLCrashReporter is a reliable open source library that provides an in-process live crash reporting framework for use on iOS, macOS and tvOS. The library detects crashes and generates reports to help your investigation and troubleshooting with the information of application, system, process, thread, etc. as well as stack traces.

The easiest way to use PLCrashReporter is by using AppCenter. However, if you want to use PLCrashReporter directly, grab the latest release at releases page.

Features

  • Uses only supported and public APIs/ABIs for crash reporting.
  • The most accurate stack unwinding available, using DWARF and Apple Compact Unwind frame data.
  • First released in 2008, and used in hundreds of thousands of apps. PLCrashReporter has seen a tremendous amount of user testing.
  • Does not interfere with debugging in lldb/gdb
  • Easy to integrate with existing or custom crash reporting services.
  • Backtraces for all active threads are provided.
  • Provides full register state for the crashed thread.

Prerequisites

  • Xcode 11 or above.
  • Minimum supported platforms: iOS 9, macOS 10.9, tvOS 9, Mac Catalyst 13.0.

Decoding Crash Reports

Crash reports are output as protobuf-encoded messages, and may be decoded using the CrashReporter library or any Google Protocol Buffers decoder.

In addition to the in-library decoding support, you may use the included plcrashutil binary to convert crash reports to apple's standard iPhone text format. This may be passed to the symbolicate tool.

plcrashutil convert --format=iphone example_report.plcrash | symbolicatecrash Future library releases may include built-in re-usable formatters, for outputting alternative formats directly from the phone.

Building

Prerequisites

  • A Mac running macOS compliant with Xcode requirements.
  • Xcode 11 or above.

Also, next optional tools are used to build additional resources:

Building

  • Open a new window for your Terminal.

  • Go to PLCrashReporter's root folder and run

    xcodebuild -configuration Release -target 'CrashReporter'
    

    to create binaries for all platforms.

Contributing

We are looking forward to your contributions via pull requests.

To contribute to PLCrashReporter, you need the tools mentioned above to build PLCrashReporter for all architectures and protobuf-c to convert Protocol Buffer .proto files to C descriptor code.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.