fix memsize_node when called on xmlAttrs #2924
Merged
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.
What problem is this PR intended to solve?
The
properties
field of anxmlNode
element points to anxmlAttr
.The first few fields of
xmlAttr
are in common withxmlNode
, but notthe
properties
field which doesn't exist in anxmlAttr
.The
memsize_node
function was passing anxmlAttr
to a recursive calland then trying to do the same with the properties of that.
This led to type confusion and subsequent crashes.
Fixes: #2923
Have you included adequate test coverage?
Yes.
Does this change affect the behavior of either the C or the Java
implementations?
It fixes a crash in the C implementation of an ObjectSpace method that is not implemented in JRuby.