| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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
|
|
Also update minimum CMake version.
|
|
cause bugs and also issues with C++20
|
|
|
|
|
|
|
|
thrown exception
Probably should have done this sooner, just lets the user continue analysis, rtti exceptions are continuable from the view of analysis.
|
|
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
|
|
|
|
We need to do this for RTTI info that resides in DefaultSectionSemantic sections, which will happen for some binaries where the data is placed in non-generic sections.
|
|
GCC emits a leading `*` to indicate that the type info is internal and
its name can be compared via pointer equality. It is not part of the
type name. This was only being handled when followed with `N`, but it
can apply to any mangled name.
Additionally, this updates some `std::string::find(...) == 0` calls in
the adjacent code to use `std::string::rfind(..., 0) == 0` as that bails
out of the string comparison as soon as the prefix does not match,
rather than continuing to search the entire string.
|
|
32-bit ELF binaries that are dynamically linked to the C++ runtime may
use a copy relocation for the vtable. The vtable itself will be defined
in the `.bss` section, and the copy relocation will cause the dynamic
linker to populate it at load time from the C++ runtime library.
Detect this by looking for a symbol pointing to the start of the vtable data,
two pointers before the vtable address.
|
|
introduced analysis is processed before pipeline completion.
|
|
Finish verifying VMI base class info before applying data variable and symbol
|
|
|
|
|
|
The vft will have a few fields above it, we did not verify that when we read those fields that they were readable.
Fixes https://github.com/Vector35/binaryninja-api/issues/6694
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/6692
|
|
|
|
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
|
|
Not even going to check the git blame i know this was committed at 3 in the morning
|
|
32bit support still needs some fixes for the VMI offsets and other things, but its better than it was before.
Likely need to do a little refactoring after this release to make the code less horrendous, but its fine for now.
|
|
Unlikely to be the last for initial analysis, still a good idea to check.
|
|
|
|
We really need a IsValidRange function
|
|
|
|
I have a heavy dislike for this, but I also don't really have a better way of doing this without merging the VFT processing.
|
|
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
|
|
Also allows for both processors to be ran for a single binary
|
|
Still needs to support edge cases and multiple vtables, as well as naming needs to be adjusted
|
|
|
|
|
|
|
