Reading a Crash Log

When Runlet crashes, macOS saves a crash report. To keep the app small, stable releases leave their debugging symbols out, so Runlet's own lines in that report show as bare addresses. One command turns them back into function names, files, and lines, which makes a crash report useful in an issue.

Betas keep their symbols in the app, so their reports are readable as they are.

Symbolicating a Crash Report

In Terminal, on the Mac where Runlet crashed:

curl -fsSL https://raw.githubusercontent.com/filipac/runlet/main/scripts/symbolicate-crash.sh | sh

It reads the newest Runlet crash report and prints the crashed thread with names, files, and lines. To read a specific report, or every thread, add --all and the report's path:

curl -fsSL https://raw.githubusercontent.com/filipac/runlet/main/scripts/symbolicate-crash.sh | sh -s -- --all ~/Library/Logs/DiagnosticReports/Runlet-2026-10-05-120000.ips

The script only reads the report and prints. It downloads the symbols for that version of Runlet from its GitHub release once, checks them against the release's checksums, and refuses symbols that don't belong to the build that crashed.

It needs Xcode's command line tools:

xcode-select --install

TIP

To read the script before you run it, download it first with curl -fsSLO https://raw.githubusercontent.com/filipac/runlet/main/scripts/symbolicate-crash.sh, then run sh symbolicate-crash.sh.

Finding Crash Reports

Crash reports are in ~/Library/Logs/DiagnosticReports/, named Runlet-<date>.ips. In the Console app, they're under Crash Reports.

Reporting a Crash

Open an issue on GitHub and attach the .ips file or the symbolicated lines, with:

• the Runlet version (Runlet ▸ About Runlet);
• your macOS version;
• what you were doing when it crashed.

WARNING

A crash report can contain paths from your Mac, such as your user folder, and the text of the error that stopped the app. Look it over before you post it.