Fix too strict debug assertion #11528
Merged
Conversation
This file contains 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
|
The patch itself fixes: Reported upstream here: Also other distros like Fedora is using this patch since libmad-0.15.1b-26 |
Swiftb0y
approved these changes
May 2, 2023
There was a problem hiding this comment.
code LGTM. Waiting for @JoergAtGithub to confirm that this fixes the issue.
|
This solves the problem for me! Thank you! |
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.
It seems to be not correct to use the error value after a libmad function succeeds.
This has slipped through, because the debian package of this library uses a patch that fixes the behavior.
I was able to reproduce the issue with a unpatched local build of libmad.