| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Previously we only really had a way to access the platform system call information, this was missing the system call information found in type libraries
Fixes https://github.com/Vector35/binaryninja-api/issues/7089
|
|
The python API was kept the same seeing as we are close to the release, will likely start deprecating some of those API's soon.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
duplicating work
|
|
of the _user_ variant
|
|
|
|
|
|
linear/graph view
|
|
|
|
|
|
|
|
|
|
Apparently GCC will fail the build for this in C++20.
|
|
cause bugs and also issues with C++20
|
|
|
|
|
|
|
|
This commit moves AnalyzeBasicBlocks from the binary ninja core to the
API and allows architecture plugins to optionally override
AnalyzeBasicBlocks for a custom implementation
Supply ABB inputs in BNBasicBlockAnalysisContext
Register default analyze basic blocks callback
This allows the nanomips and rust core architecture plugins to work
again while using the C++ API DefaultAnalyzeBasicBlocks
Use default ABB from Python plugins
Fix bug in API ArchAndAddr operator overload
Python APIs for basic block analysis
|
|
|
|
|
|
|
|
|
|
|
|
It was already grabbing the Lifted IL through the function object, which may not be the most up to date
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
So that users of the memory map API can know if a view has activated the memory map and adjust behavior accordingly.
|
|
|
|
|
