| Age | Commit message (Collapse) | Author |
|
|
|
- Allow extern functions to show up in a MSVC vtable
- Fix https://github.com/Vector35/binaryninja-api/issues/7871
- Share code between itanium and msvc vft analysis, it is the same logic basically
|
|
|
|
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/7705
RTTI processing with malformed sections can still cause prolonged analysis, in extreme cases like the binary in the issue needing the user to stop the RTTI processing once it gets to the Itanium RTTI pass. More work to be done, I would like to solve this with some section heuristics using the sections/segments entropy.
|
|
the previous pass
|
|
|
|
This fixes an issue with certain shared cache binaries where a VFT was placed at the tail of the const data section
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/6959
|
|
cause bugs and also issues with C++20
|
|
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/6837
|
|
Found when a vtable is constrained to a size less than the base vft, indicating a bad base vft associating most likely.
Fixes https://github.com/Vector35/binaryninja-api/issues/6840
|
|
Also adds more information to the progress text when processing vfts for both msvc and itanium
|
|
Some missing checks in case there is a billion segments (see .obj files)
|
|
If the background task gets stuck, this is the commit to ponder at
|
|
No reason to show this every time you load a binary, if someone feels strongly about seeing this say something!
|
|
Still need to allow NTR's to work in the base structure attribute.
There is still a bit of extra work that needs to be done to polish this up but there are no regressions using this.
|
|
Bunch of misc fixes and performance improvements
|
|
|