Skip to content

Commit f2b6341

Browse files
authored
docs(unreal): Sentry Crash Reporter stacktrace (#17135)
Related items: - getsentry/sentry-unreal#1312
1 parent b3bb169 commit f2b6341

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

  • docs/platforms/unreal/configuration/setup-crashreporter

docs/platforms/unreal/configuration/setup-crashreporter/index.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -227,6 +227,21 @@ To use your custom build, replace the crash reporter executable in the plugin's
227227

228228
After replacing the executable, delete the project's `Build` and `Intermediate` directories and rebuild the project to ensure the updated binary is picked up.
229229

230+
### Stacktrace Display
231+
232+
The Sentry Crash Reporter can display a symbolicated stacktrace of the crashed thread, allowing users to review the call stack directly in the crash dialog before submitting the report.
233+
234+
This feature requires client-side stack walking, which is supported through two backend configurations:
235+
236+
- **[Native backend](/platforms/unreal/configuration/native-backend/)**: Performs stack walking and symbolication automatically using the platform's debug APIs. No additional configuration is needed.
237+
- **Crashpad backend**: Requires a custom build of `sentry-native` with the `CRASHPAD_ENABLE_STACKTRACE` CMake flag enabled.
238+
239+
<Alert>
240+
241+
For **Shipping builds**, the stacktrace can only be symbolicated if debug information is available at runtime. Enable **Include Debug Files in Shipping Builds** in **Project Settings > Packaging** to ensure function names are resolved in the crash reporter dialog.
242+
243+
</Alert>
244+
230245
## Upload Debug Symbols
231246

232247
To allow Sentry to fully process native crashes and provide you with

0 commit comments

Comments
 (0)