ZiskGuest: enable stacktrace data to facilitate possible GVM resolution#11234
Merged
Conversation
Tests show that GVM resolution depends on metadata that is being stripped away if --no-stacktrace-data is added to the bflat's command line. This patch removes this flag and improves guest's ability to perform GVM resolution, reducing number of unpredictable bugs. Signed-off-by: Maxim Menshikov <maksim.menshikov@nethermind.io>
LukaszRozmej
approved these changes
Apr 18, 2026
rubo
approved these changes
Apr 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Tests show that GVM resolution depends on metadata that is being stripped away if --no-stacktrace-data is added to the bflat's command line.
This patch removes this flag and improves guest's ability to perform GVM resolution, reducing number of unpredictable bugs.
Changes
Types of changes
What types of changes does your code introduce?
Testing
Requires testing
If yes, did you write tests?
Documentation
Requires documentation update
Requires explanation in Release Notes