[Bug]: Unreal helper reading FName names incorrectly #7
Labels
area: unreal
bug
Issue reports behavior which is not expected.
high priority
Issue is of high priority.
What helper class does this issue occur on?
Unreal
Description
The following issue was discovered when attempting to use the Unreal helper with Scorn. @just-ero and I recently observed that when trying to read FName names from the FName pool, the strings being read appear to be offset by 6 bytes which causes an over-read, resulting in mangled names which, in turn, cannot be converted into valid identifiers.
While the objects are (apparently) identified correctly, given that addresses do show up under
ue.UObjects
, not having proper names makes them unreachable throughMake<T>
.Reproduction Steps
Error Messages
Regression?
See potential causes and fixes
Potential Causes and Fixes
While this could potentially be a knock-on from a recent change to fix an AOB scan error (
GUObjectArray signature could not be resolved
), we don't have confirmation yet.In addition, this could also be caused by some struct alignment problems.
The text was updated successfully, but these errors were encountered: