Fix the retrieve of the UNIX address as an UnsafeMutablePointer for b… #177
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.
…ig endian
Description
When retrieving the UNIX address as an UnsafeMutablePointer, the current code was only for little endian. Therefore, on big endian platform, the field, i.e.,
sa_family_t
, of such an UnsafeMutablePointer cannot be correctly recovered.Motivation and Context
The fix is to swap the byte mapping to address of
afUnixShort
, which is anUInt16
on big endian platform.How Has This Been Tested?
Run
swift test
, all tests got passed. Also, failures inKitura
because of this issue got fixed after the fix.Checklist: