Skip to main content
emisar

Symbolicator native symbolication

v0.2.0

Debug native crashes with Symbolicator and keep the host it runs on healthy. Symbolicate a stack trace, a minidump, or an Apple crash report against the debug files the operator's configured sources hold, follow a request that runs long, and manage what that costs: liveness, build version, the cache footprint filling the disk, and the cleanup — previewed before it runs. Nothing here can publish or alter a symbol; Symbolicator has no ingest path. For the Sentry API itself, see the sentry pack.

9 allowed by default 1 need approval by default
Pack ID
symbolicator
Vendor
emisar
OS
linux
Actions
10
Required binaries. Install these on the host before relying on the pack — an action that calls a missing one fails at run time.
symbolicator curl jq

Install

emisar pack install fetches this pack, re-validates it, and verifies its content hash against the --hash below — the exact bytes this page was rendered against, so a tampered copy is rejected — before copying it into the runner's packs dir. The command reloads a running daemon itself; no manual restart.

on the runner host 
sudo emisar pack install symbolicator --hash sha256:a122dce646e6bdeb81aa5513436a8cf7b9a99bfbbd477dbc6cf9e96aef1b869e

Actions 10 total

View on GitHub
  • symbolicator.cache_usage script low

    Symbolicator cache footprint

    Show how much disk each Symbolicator cache holds, largest first, with the filesystem underneath it. The caches — objects, symcaches, cficaches and the rest — are what fills a symbolication host, and they grow at very different rates, so this is the read to take before deciding whether a cleanup is the answer.

    View source on GitHub
  • symbolicator.cleanup exec medium

    symbolicator cleanup

    Delete the cache entries that have gone unused past their configured retention, reclaiming disk. This is Symbolicator's own routine maintenance, bounded by the retention windows in its configuration — not a wipe. Preview it with symbolicator.cleanup_preview first.

    View source on GitHub
  • symbolicator.cleanup_preview exec low

    symbolicator cleanup --dry-run

    Show what a cache cleanup would remove and what it would keep, per cache, without deleting anything. Symbolicator prints retained and removed byte counts for each cache, so this is the read that decides whether symbolicator.cleanup is worth running.

    View source on GitHub
  • symbolicator.config_show exec high

    Show symbolicator config.yml

    Dump the Symbolicator configuration this host runs — cache root, retention windows, bind address, and the symbol sources. Reading it is how you explain why a cleanup reclaimed nothing or why a symbol never resolves. High risk on purpose: the sources block is operator-authored and routinely holds S3, GCS, or HTTP credentials, so the whole file is treated as secret-bearing rather than trusted to a pattern.

    View source on GitHub
  • symbolicator.health exec low

    GET /healthcheck

    Check whether Symbolicator is serving on this host. Answers "ok" while the HTTP server is up; a connection error means the service is down or bound somewhere other than SYMBOLICATOR_URL.

    View source on GitHub
  • symbolicator.request_status exec low

    GET /requests/<id>

    Show the status of one symbolication request by its id — whether it is still pending or has completed, and its result when it has. Use it when Sentry reports a symbolication that never came back. An unknown or expired id answers 404.

    View source on GitHub
  • symbolicator.symbolicate exec low

    POST /symbolicate

    Symbolicate a native stack trace — turn instruction addresses into function names, files, and line numbers using the debug files this Symbolicator already has access to. Send the crash's modules and frames; the symbols come from the sources the operator configured, never from the request.

    View source on GitHub
  • symbolicator.symbolicate_apple_crash exec low

    POST /applecrashreport

    Symbolicate an Apple crash report already on this host — the iOS or macOS .crash text a device produced — against the debug files this Symbolicator has access to. Answers with the symbolicated result, or with a request id to follow using symbolicator.request_status when the work runs long.

    View source on GitHub
  • symbolicator.symbolicate_minidump exec low

    POST /minidump

    Symbolicate a minidump already on this host — the crashing thread, its stack, and the loaded modules, resolved against the debug files this Symbolicator has access to. Answers with the symbolicated result, or with a request id to follow using symbolicator.request_status when the work runs long.

    View source on GitHub
  • symbolicator.version exec low

    symbolicator --version

    Show the Symbolicator build installed on this host — release version and git commit. Reports the binary on disk, which is what a restart would start.

    View source on GitHub
← Back to registry
Pack reference Publish your own →