Debug Information Files
Debug information files allow Sentry to extract stack traces and provide more information about crash reports for most compiled platforms. Information stored in debug files includes original function names, paths to source files and line numbers, source code context, or the placement of variables in memory. Sentry can use some of this information and display it on the issue details page.
Each major platform uses different debug information files. We currently support the following formats:
- dSYM files for iOS, iPadOS, tvOS, watchOS, and macOS
- ELF symbols for Linux and Android (NDK)
- PDB files for Windows and .NET
- Breakpad symbols for all platforms
- WASM files for WebAssembly
- ProGuard mappings for Java and Android
Source maps, while also being debug information files, are handled differently in Sentry. For more information see Source Maps in sentry-cli.
Sentry requires access to debug information files of your application as well as system libraries to provide fully symbolicated crash reports. You can either upload your files to Sentry or put them on a compatible Symbol Server to be downloaded by Sentry when needed.
After they have been uploaded, debug information files can be viewed and managed from the Debug Files section in the associated
From the Project Details page, click into settings, then click on Debug Files in the page navigation.
ProGuard files are listed separately, in the ProGuard section of the project settings page.
Debug Files have a retention period of 90 days, using a time to idle expiration mechanism. This means that uploaded debug files are retained for as long as they are actively being used for event processing. Once a debug file has not been used to process incoming events for at least 90 days, it will automatically expire and be eligible for deletion.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").