fixed uninitialized variable#246
Merged
padelsbach merged 1 commit intoAug 5, 2025
Merged
Conversation
printAmt was not initialized to 0
padelsbach
approved these changes
Aug 5, 2025
Contributor
|
Good catch, thanks for the PR. This fix is also captured in #234, but that PR will take a bit longer. |
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.
printAmt was not initialized to 0.
This never showed up before so I assume it is related to my configuration.
printAmtis only uninitialized when there is no public or private key specified (hasPub, hasPriv). Which are set like this:I found this while building with the configuration specified in the documentation (Section 3.3.1 - 3.3.3)
OpenSSL:
wolfSSL:
wolfProvider: