[gdb] Allow gdb.Value to take a Buffer plus a Type#16006
Merged
Conversation
Support for this was introduced in a commit in 2019, which I think means it's been available since gdb 9.1 If a type is passed that is not None, it always goes through the buffer protocol, which interestingly means you can't pass an existing gdb.Value together with a type. You have to use the cast method for that purpose.
Contributor
|
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
srittau
approved these changes
Jul 11, 2026
Contributor
Author
|
Thanks! |
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
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.
Support for this was introduced in a commit in 2019, which I think means it's been available since gdb 9.1
Commit that introduced the feature: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=fe07eca59d0544eb6c56c3559da9ceece23cae6e
If the type value passed is None or there is no second argument, it falls back to its "convert value from python" logic which tries a few things (bool, long, float, unicode string, gdb.Value, gdb.LazyString).
If instead the type is passed and is not None, it will always go through the buffer protocol, which interestingly means that you can't pass a gdb.Value nor a gdb.LazyString to the variant of the constructor with a type.