# Debug Information | Sentry for Native

To allow Sentry to fully process native crashes and provide you with symbolicated stack traces, you need to upload *Debug Information Files* (sometimes also referred to as *Debug Symbols* or just *Symbols*). We recommend uploading debug information during your build or release process.

For all libraries where you'd like to receive symbolication, **you need to provide debug information**. This includes dependencies and operating system libraries. If you are not sure which files are required, go to *Project Settings > Processing Issues*, which shows a list of all the necessary files and instructions to retrieve them.

In addition to Debug Information Files, Sentry needs *Call Frame Information* (CFI) to extract accurate stack traces from minidumps of optimized release builds. CFI is usually part of the executables and not copied to debug symbols. Unless you are uploading Breakpad symbols, be sure to also include the binaries when uploading files to Sentry.

For more information on uploading debug information and their supported formats, see [Debug Information Files](https://docs.sentry.io/data-management/debug-files.md).
