[release/9.0-staging] Fix generation of minidump #115738
Merged
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
tommcdon
approved these changes
May 19, 2025
Open
3 tasks
This was referenced May 28, 2025
jeffschwMSFT
approved these changes
May 28, 2025
|
Tagging subscribers to this area: @tommcdon |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #115562 to release/9.0-staging
/cc @thaystg
Customer Impact
Some mini dumps generated by the runtime are missing information and the managed callstack can't be inspected.
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
We got a full dump and generated a mini dump from it and with the fix the mini dump is with the managed callstack information correctly.
Risk
Low risk, only added another try catch as there are many others in the code.