Peter LaFosse

Ok I looked into this and the way that I think this needs to happen here we need to handle the specific swift specific string pointer encoding via a workflow....

The original binaries in this issue no longer exhibit and issue. When the stack becomes unresolved you need to "Set Stack Adjust" to correct the issue: For the example provided...

I've tried to reproduce this by scanning dozens of binaries for variables without types. I can't make progress on this until I have a repro of a typeless variable.

Currently the way platform types work is they're all imported directly into the BNDB. On BNDB reload the current set of platform types aren't imported as they could overwrite things...

There is clearly a documentation issue here. The `offset` is actually only used for StructureMember offsets. Not for generalized pointer offsets. What you want here is `pointer_base_offset` ``` >>> foo...

Looks like there is no public API for creating pointer to structure member types. This only exists inside the core. This is only part of the interface and the other...

The issue here is that the jump table is in a writable section. If you create a datavariable of type `const uint64_6[0x100]` everything will resolve itself. This is a very...

Perhaps a tooltip would be acceptable?

@emesare This seems to correspond to ``` commit f55a1eef2bb62212a934c01058b2a32faddbbcec Author: Mason Reed Date: Sun May 4 21:20:32 2025 -0400 Bump API (skip-note) ``` which corresponds with ``` commit 178887ba4d503838c444a0c976ac5538117fd2fb Author:...

If not could you provide just the bytes of the disassembly?