I am trying to debug a crashed (or hanging) app. How do I get the diagnostic files from the crash?
Individual crash reports are stored in ~/Library/Logs/CrashReporter but there is a system wide log collection tool called sysdiagnose.
Once you start experiencing the issue, hold down the 4 control keys and then press the period "." key. shift+control+option+command+.
After about 15 seconds, a Finder window will open with a sysdiagnose file highlighted.
This shortcut simply executes the
sysdiagnose command, so if you are familiar with the terminal and want to pass in a process ID, you can get enhanced debugging information about that specific program. The key shortcut calls the tool with no arguments and captures the basic report only.
This shell script(on 10.8 and lower) and executable program by the same name on 10.9:
- gathers system-wide diagnostic information
- is integral to OS X Lion and greater
- is not available as a separate download
- is not open source (I have asked Apple to make it so).
Preparing for the keyboard-only approach to sysdiagnose
In Terminal, run the following command.
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.stackshot.plist
- if prompted for a password, enter your admin password for the operating system
- that's a one-off, no need to repeat the command.
Take a written note of the following key chord, you'll need it later:
Diagnosis by the system
When an issue occurs:
- use the key chord
- for at least ten seconds, touch nothing
- allow maybe five or ten minutes for all parts of the
sysdiagnoseroutine to complete – simply wait as long as you can (there'll be no on-screen indication of progress)
- Finder should open a window to the end result.
In rare cases, an issue may prevent sysdiagnose from completing (I have made improvement suggestions to Apple). If this happens – if you're sure that you have waited long enough – it may be sensible to restart the Mac. Then:
- in Finder, go to
- seek a file or folder with a name beginning sysdiagnose_
- if that file or folder exists, move it to a convenient place – your desktop, maybe.
Without the key chord, you can run sysdiagnose from the command line (see below, Apple manual page). But it's often more useful, or necessary, to use the chord – so be prepared.
Whilst I don't encourage carelessness, you can be a little careless with Control-Option-Command-Shift-. … if you struggle to avoid the fn key on your laptop, don't worry; including it by accident should not prevent the run of
Human analysis of diagnosis by the system
Hint: someone might like to ask a separate question about analysing the results of
sysdiagnose – a more generalised answer could be useful.
If sysdiagnose_… from the
/tmp area is a file
Presence of a
sysdiagnose_….tar.gz file indicates that all parts of the
sysdiagnose routine completed, and that the results were archived. If you wish, open the archive – its contents will appear as a folder.
If sysdiagnose_… from the
/tmp area is a folder
Presence of a
sysdiagnose_… folder (not a
.tar.gz file) indicates that either:
- the routine was interrupted before completion; or
- some part of the routine could not complete.
Within the archive/folder
Some files are human-readable and may help to troubleshoot an issue.
Other files are more developer-oriented.
- How does 'stuck' (in results of 'top') relate to 'not responding' (in Activity Monitor), 'spin' or 'hang'?
For an incomplete run of
sysdiagnose it may be useful to focus some attention on files that are abnormally empty …
Technical and other notes
Some of what's above is a more generic edition of an accepted answer that appears elsewhere.
Diagnostic and usage information, other files of interest
Be guided by the log list in Console:
Expect to find files at the following paths:
To find existing diagnostic or crash files, open Console app and find the files in User Reports (located at
~/Library/Logs/DiagnosticReports) in or System Reports (located at
/Library/Logs/DiagnosticReports) sections. See: Where can I find my crash logs?
As per official
sysdiagnose instructions for macOS, you can trigger a
sysdiagnose either by:
Note: To access above link, you need to log-in to Developer Apple site first.
Briefly press the following keys simultaneously:
and wait. The
sysdiagnoseprocess can take 10 minutes to complete. Once finished, Finder should automatically appear showing the generated file in
sysdiagnosefrom Terminal by entering this command:
To generate crash core dumps, see: How to generate core dumps on macOS?
You must log in to answer this question.
protected by bmike♦ Nov 18 '18 at 20:27
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?