Skip to content
More useful crash logs
Branch: master
Clone or download
Muirey03 No armv7 support
(sorry armv7 users)
Latest commit 93c1890 May 9, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
AppSupport A12 support May 7, 2019
Frameworks A12 support May 7, 2019
Libraries Update libbulletin.dylib May 7, 2019
MobileGestalt A12 support May 7, 2019
cr4shedgui A12 support May 7, 2019
cr4shedsb No armv7 support May 8, 2019
libsymbolicate A12 support May 7, 2019
rocketbootstrap A12 support May 7, 2019
.gitattributes Initial commit Dec 5, 2018
.travis.yml A12 support May 7, 2019
Cr4shed.plist Fix respring loops on iOS 12 Mar 3, 2019
Makefile No armv7 support May 8, 2019
README.md Update README Mar 1, 2019
Tweak.xm A12 support May 7, 2019
control
symbolication.h A12 support May 7, 2019

README.md

Cr4shed

More useful crash logs at /var/tmp/crash_logs

This is a useful little package designed to help developers identify and fix crashes that have been reported to them by their users. It generates a crash log in /var/tmp/crash_logs including information such as the process that crashed, the exact reason for the crash, the dylib that caused the crash and the entire call stack when the crash occurred.

This is super useful if someone reports a crash to you and you can't work out what the issue is purely from the crash log. (Is also extremely useful for identifying causes of crashes in development). This report should be everything you need to work out exactly why the crash occurred.

This is designed to work alongside CrashReporter, not to replace it. It provides information that CrashReporter cannot provide and is usually all you need to identify the cause of the crash, but CrashReporter can still prove useful too for crashes that aren't caused by NSExceptions.

You can’t perform that action at this time.