| Age | Commit message (Collapse) | Author |
|---|
|
Another set of bugs caused by undo and main thread actions, when will it end
|
|
Was not able to find the core plugin in the plugins directory
|
|
Removing the nesting because we now scope view plugin commands out of the context menu
|
|
|
|
|
|
- Added FFI
- Added a sidebar to the UI
- Added project, directory and archive processing
- Added generic `Container` interface for extensible stores of WARP data
- Fixed type references being constructed and pulled incorrectly
- Added HTML, Markdown and JSON report generation
- Made the WARP information added as an analysis activity
- Flattened the signatures directory, the target information is stored in the file now
- Matched function information is stored as function metadata in the database to reliably persist, alongside the function GUID
- Split the matching out from the application, allowing you to match on a given function without applying it
- Added more/better tests
- Added support for binaries with multiple architectures, the functions are now also queried based off the Target, see WARP spec for more details
- Greatly improved support for RISC architectures, see WARP spec for more details
- Greatly improved UX when loading files after the fact, will now sanely rerun the matcher
- Omitted the function type if not a user type, this greatly reduces file size
- Improved support for functions that reference a page aligned base pointer, see WARP spec for more details
- Removed some extra cache structures that were causing erroneous behavior
- Fixed edge-case in LLIL traversal missing some constant pointers, this was a bug in the Rust bindings
- Added support for function comments
- Made long running tasks, such as generating, matching and loading signatures, cancellable where possible
- Made function constraints more versatile, allowing for easy extensions in the future, see WARP spec for details
- Added options to signature generation, such as what data to store, and whether to compress the data or not
- Made all long running tasks prompt the user for required information before the task starts, allowing users to "set it and forget it" and not have to baby sit the finalization of the task
- Myriad of other changes to the actual WARP format that impact performance, file size and general feature set, see https://github.com/Vector35/warp for more details
|
|
Highlights all variant instructions and blacklisted instructions
Variant instructions are highlighted red, blacklisted will be orange.
|
|
Need to do this for exposing to FFI and things like render layers
|
|
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/6959
|
|
|
|
|
|
Also update minimum CMake version.
|
|
cause bugs and also issues with C++20
|
|
|
|
|
|
|
|
Fixes #6900
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 don't do enough with the lifted il != non lifted il to justify the bound.
This makes modifying IL much less work as the historical lifted il bound is gone.
|
|
|
|
This is being done to reduce complexity in function signatures, specifically many of the strings we are passing ultimately should be new types themselves instead of "just strings", things such as type ids.
Another place which was confusing was dealing with filesystem related APIs, this commit turns most of those params into a stricter `Path` type.
This is bringing the rust api more inline with both python and C++, where the wrapper eagerly converts the string into the languages standard string type.
Special consideration must be made for symbols or other possible non utf-8 objects.
This commit will be followed up with one that adds the `IntoCStr` bound on API's we want to keep as invalid utf-8 so we can for example, get section by name on a section with invalid utf-8.
|
|
- Removed `to_string` shortcut from `BnString`.
- Misc formatting
|
|
|
|
conversion can be tolerated
Still need to go and audit all usage, but realistically the most important places to give the user control are with symbols, where the data can come from non utf8 sources
This is still incomplete, I just looked for usage of -> BnString so any other variant was omitted.
|
|
|
|
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.
|
|
|
|
|
|
This is apart of https://github.com/Vector35/binaryninja-api/issues/6678
|
|
introduced analysis is processed before pipeline completion.
|
|
Finish verifying VMI base class info before applying data variable and symbol
|
|
|
|
|
|
|
|
- Do not add binary base to function address twice when a symbol with that function's raw name already exists
- Load eh_frame/debug_frame from base bv instead of debug bv and make calculated cie offset ranges relative to bv start
- Fix dwarf raw name resolution not resolving specification
- Try to load eh_frame/debug_frame from both raw and normal views in dwarf import
|
|
|
