Reflection Library crash inspecting certain BoundGeneric types #32983
Conversation
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
If the parent of a BoundGeneric type is not a NominalType (for example, if the Parent was an ObjCClass type) the `getDepth()` method would end up reading a Parent reference from uninitialized memory. The resulting garbage pointer would cause a crash in the tool that was using the reflection library (leaks, instruments, etc.) Of course, this does not always result in a crash, since the memory in question is frequently zeroed, resulting in a nil pointer that is safely detected. Resolves rdar://54173375
|
@swift-ci Please test |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
|
@swift-ci Please test Linux |
|
Build failed |
|
@swift-ci Please smoke test Linux |
|
@swift-ci Please smoke test |
|
@swift-ci Please test |
|
Build failed |
tbkka
added a commit
to tbkka/swift
that referenced
this pull request
Jul 20, 2020
…lang#32983) * Reflectio Library crash inspecting certain BoundGeneric types If the parent of a BoundGeneric type is not a NominalType (for example, if the Parent was an ObjCClass type) the `getDepth()` method would end up reading a Parent reference from uninitialized memory. The resulting garbage pointer would cause a crash in the tool that was using the reflection library (leaks, instruments, etc.) Of course, this does not always result in a crash, since the memory in question is frequently zeroed, resulting in a nil pointer that is safely detected. Resolves rdar://54173375 * Fix compile
tbkka
added a commit
that referenced
this pull request
Jul 21, 2020
… (#33008) * Reflectio Library crash inspecting certain BoundGeneric types If the parent of a BoundGeneric type is not a NominalType (for example, if the Parent was an ObjCClass type) the `getDepth()` method would end up reading a Parent reference from uninitialized memory. The resulting garbage pointer would cause a crash in the tool that was using the reflection library (leaks, instruments, etc.) Of course, this does not always result in a crash, since the memory in question is frequently zeroed, resulting in a nil pointer that is safely detected. Resolves rdar://54173375 * Fix compile
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.
If the parent of a BoundGeneric type is not a NominalType (for example, if the
Parent was an ObjCClass type) the
getDepth()method would end up reading aParent reference from uninitialized memory. The resulting garbage pointer
would cause a crash in the tool that was using the reflection library
(leaks, instruments, etc.)
Of course, this does not always result in a crash, since the memory in question
is frequently zeroed, resulting in a nil pointer that is safely detected.
This changes
getDepth()to detect unrecognized types and return zero.Resolves rdar://54173375