Open VisualEhrmanntraut opened 1 week ago
>>> bv.types.get("IOMemoryCursor::PhysicalSegment") is None
True
>>> bv.type_names.index("IOMemoryCursor::PhysicalSegment")
7540
another variant: shows correct name, but actually points to different type
What's the value of current_function.symbol.raw_name
? The type name may be coming from that, or could be some artifact of the id being empty.
Version and Platform (required):
Bug Description: getting the demangled function type and assigning it doesn't always work correctly. it doesn't matter if the type is defined or not.
Steps To Reproduce:
this is happening even though
IOMFB::AppleRegisterStream
is defined andIOMemoryCursor::PhysicalSegment
doesn't even exist in the bndb, I have no idea where it is pulling that from.Expected Behavior:
current_function.type.parameters[0]
should've beenIOMFB::AppleRegisterStream* arg1
.Additional Information: working with a bndb that was opened before iOS typelib was introduced, however I am uncertain of its relevancy to the issue.