Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The pythonic type doesn't seem to work when adding or assigning it to a field #156

Closed
arizvisa opened this issue May 23, 2022 · 3 comments
Closed
Assignees
Labels

Comments

@arizvisa
Copy link
Owner

As reported by someone in private, the pythonic type does not actually work when adding it to a field. This is actually because IDA deals with this specially (using FF_-based flags which aren't based on the size). So, when I implemented it...it was definitely hacked into place.

This involves fixing two things, one of them is the typemap dissolver and the other is related to why IDA throws up a messagebox whenever I try to assign flags to the type.

@arizvisa
Copy link
Owner Author

arizvisa commented May 23, 2022

The mapping of the type keyword seems to have been fixed, but the API that's being used to fetch the type seems to be raising a warning box after the type has been applied. The warning that's being displayed is "struct->til conversion failed". I imagine this has to do with the flags that're being applied as in my tests only the MS_1TYPE flag seems to apply to a field and I'm pretty sure I'm setting both to deal with things other than structure members. Hence, this isn't entirely fixed and will still need looking into.

For now, PR #157 is currently working on resolving this issue.

arizvisa added a commit that referenced this issue May 26, 2022
Fixed the pythonic `type` so that it creates its reference in the correct size and will also be decoded properly.
@arizvisa
Copy link
Owner Author

Closing as this was fixed by PR #157.

@arizvisa
Copy link
Owner Author

Apparently the database.get.structure function was not decoding the pythonic pointer type correctly. This was fixed by commit 8411220.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant