problem: zero-sized messages cause assertion when glibc assertion are on#3705
Merged
bluca merged 1 commit intozeromq:masterfrom Oct 7, 2019
Merged
problem: zero-sized messages cause assertion when glibc assertion are on#3705bluca merged 1 commit intozeromq:masterfrom
bluca merged 1 commit intozeromq:masterfrom
Conversation
Solution: when a zero-sized message is encoded or decoded avoid mem copy
Member
Author
|
@bluca this is what causes the Fedora issue. It was hard to find... maybe we should enable the glibcxx assertions when developing |
Member
Author
|
on in one of the builds of travis... |
Member
|
Great catch! Yes enabling that sounds like a good idea |
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
2 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.
Solution: when a zero-sized message is encoded or decoded avoid mem copy