Add support for printing crash stack traces to the game log (Microsoft) #1177
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # CHANGELOG.md
…ry-unreal into feat/crash-logs-microsoft
# Conflicts: # plugin-dev/Source/Sentry/Private/Windows/WindowsSentrySubsystem.cpp
Contributor
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
plugin-dev/Source/Sentry/Private/Microsoft/MicrosoftSentryCrashLogger.cpp
Show resolved
Hide resolved
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
plugin-dev/Source/Sentry/Private/Microsoft/MicrosoftSentryCrashLogger.cpp
Show resolved
Hide resolved
sample/Source/SentryPlayground/SentryPlaygroundGameInstance.cpp
Outdated
Show resolved
Hide resolved
mujacica
approved these changes
Dec 22, 2025
This was referenced Dec 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up PR for #1170 that enables printing crash stack traces to the game log for all Microsoft platforms (Windows, Xbox).
The Windows-specific crash logger implementation which performs stack walking on a separate thread to avoid issues with memory allocations during certain crash types (e.g. stack overflows or memory corruption) has been moved to the
Microsoftsubdirectory. The internal APIs it relies on are also supported on Xbox so there is no need to duplicate this largely generic code forXSXandXB1targets.Unlike on Windows, the Xbox platform-specific implementation of
FPlatformStackWalk::StackWalkAndDumpignores the crash context input parameter and always performs stack walking for the current calling thread (which in this case is the logger thread). This results in an irrelevant call stack being captured. To work around this,PlatformStackWalk::CaptureThreadStackBackTraceis used instead and the captured frames are then manually converted into human-readable strings before flushing the logs.Related issues: