Symalot
Small Python bindings for the Rust libraries used to process native crash reports and debug files. The initial interface serves Bugsink's minidump handling.
Initial API
debug_file_kind(data)identifies exactly one debug object; returns e.g."dbg".generate_cfi(data)returns ASCII unwind information as Python bytes.lookup_addresses(data, addresses)parses once and returns one list of source locations per module-relative address, preserving input order and inline frames. Locations havefunction_name,filename(full path), andlineattributes.normalize_debug_id(value)returns a canonical debug ID, preserving PDB age.minidump_modules(data)returns loaded modules without unwinding threads; use it to find the CFI files needed before processing a dump.process_minidump(data, cfi=None)returns crash metadata, system information, loaded modules, and threads with instruction addresses and frame trust.cfimaps debug IDs to ASCII unwind bytes. Processing uses only these inputs, with no filesystem or network symbol lookup.
License and upstream material
Copyright 2026 Bugsink, under the MIT license in LICENSE.
Adapted symbolic tests and copied fixtures live in tests/upstream/getsentry_symbolic, with Sentry's copyright and upstream MIT license kept there. The minidump fixtures in tests/fixtures carry Google's copyright and their own BSD license.
Rust dependencies retain their own copyrights and licenses.
Metadata
Release files for symalot 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| symalot-1.0.0.tar.gz | 840.0 kB | With provenance | Details for symalot-1.0.0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| symalot-1.0.0-cp311-abi3-manylinux_2_28_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ x86-64 | Details for symalot-1.0.0-cp311-abi3-manylinux_2_28_x86_64.whl |
| symalot-1.0.0-cp311-abi3-manylinux_2_28_aarch64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ ARM64 | Details for symalot-1.0.0-cp311-abi3-manylinux_2_28_aarch64.whl |
| symalot-1.0.0-cp311-abi3-macosx_11_0_arm64.whl | CPython 3.11 | abi3 | macOS 11.0+ ARM64 | Details for symalot-1.0.0-cp311-abi3-macosx_11_0_arm64.whl |
| symalot-1.0.0-cp311-abi3-macosx_10_12_x86_64.whl | CPython 3.11 | abi3 | macOS 10.12+ x86-64 | Details for symalot-1.0.0-cp311-abi3-macosx_10_12_x86_64.whl |
Total release size: 15.1 MB
Release files / symalot-1.0.0.tar.gz
| Download URL | symalot-1.0.0.tar.gz |
|---|---|
| Size | 840.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a4f1baab726742e092016830796eae013723365d290c10d327f443d98d4deec
|
|
BLAKE2b-256 checksum How to use checksums |
7e4fcfe4b2555f4a7843c6c35a6c3877d93008a30635d8fe4d67f4ed375a06f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / symalot-1.0.0-cp311-abi3-manylinux_2_28_x86_64.whl
| Download URL | symalot-1.0.0-cp311-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.7 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
bc6ca69b564ec4385203601e7e5f4be21072260855579cecd52bb82f7e16851b
|
|
BLAKE2b-256 checksum How to use checksums |
bda7160553ef16cb11f989ef66a949b802f54c99601e6303a60109cb1ce224a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / symalot-1.0.0-cp311-abi3-manylinux_2_28_aarch64.whl
| Download URL | symalot-1.0.0-cp311-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.7 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
f3b2020dde88938e69b625bd8e8c0245b6c411681fb961f8e07cb4434cde98d3
|
|
BLAKE2b-256 checksum How to use checksums |
9b75b195c9aabcb5364b7a6220325b75b1551cc22b008dc9d213996e418a68e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / symalot-1.0.0-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | symalot-1.0.0-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
44ff98a5e96141f074860fb4ca929f5fc6e624c1d2db5663362e42aad5c591b9
|
|
BLAKE2b-256 checksum How to use checksums |
7a630d751bce01c773ce331b442d924d872006917480aa2b8284cb7e901f617c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / symalot-1.0.0-cp311-abi3-macosx_10_12_x86_64.whl
| Download URL | symalot-1.0.0-cp311-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.11 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
369d5d42e2c32b7dd420772e34d3065f738b1a279cfd5de308f32552d2734cb2
|
|
BLAKE2b-256 checksum How to use checksums |
9ab02b599e1e937cce4552c83d59da7b13dfa61f67e81e367e39530ba1eb8ed8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logSecurity for symalot 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for symalot-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.