Fix building with GVM_RESOLUTION_TRACE defined #118160
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
`MethodNameAndSignature` no longer has the `string`-typed property.
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a compilation issue when building with the GVM_RESOLUTION_TRACE preprocessor definition enabled. The fix addresses the removal of the string-typed property from MethodNameAndSignature, updating debug trace statements to use the correct property access pattern.
Key changes:
- Updates two debug trace statements to use
slotMethod.Nameinstead ofslotMethod.NameAndSignature.Name
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
jkotas
approved these changes
Jul 29, 2025
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.
MethodNameAndSignatureno longer has thestring-typed property.