| Age | Commit message (Collapse) | Author |
|
This reverts commit 72fcf44f3731ade3cf1310da55f633f1cb9069ce.
|
|
|
|
Also adds support for parsing bitfields in PDB, DWARF and SVD plugins
WIP: API needs to be considered more, also need to find type related apis that may need to be rethought.
|
|
`get_data`
We want to provide no value in the case of the key not having an associated value
|
|
|
|
Also adds an example plugin and misc rust fixes / documentation.
This is a continuation of https://github.com/Vector35/binaryninja-api/pull/6721
Co-authored-by: rbran <lgit@rubens.io>
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/7268
|
|
|
|
expr index
|
|
`Workflow::new` is replaced by `Workflow::build` that returns a
`Builder` type that supports the operations that mutate a workflow, such
as registering activities.
`Workflow::instance` is replaced by `Workflow::get` to make clear that
it is intended to look up an existing workflow.
`Workflow::cloned` is introduced to wrap the common pattern of
retrieving an existing workflow and cloning it with the same name in
order to modify it.
`Builder::activity_before` / `Builder::activity_after` are introduced to
wrap the common pattern of registering an activity then inserting it
before or after a given activity.
|
|
|
|
- Fix cmake clean not cleaning target docs
- Fix not prioritizing enterprise remote in collab tests
- Some misc formatting
- Fix incorrect assert in binary loading
|
|
|
|
|
|
To allow for creating reports outside the context of a view
|
|
|
|
|
|
|
|
Also make `Project::file_by_path` take a `Path`.
|
|
The function name is redundant, just pull from the symbol
|
|
|
|
This test makes sure that initial analysis is not tainting functions
|
|
|
|
This affects mainly users creating an empty raw view headlessly and adding a function.
|
|
`MediumLevelILFunction::instruction_from_index`
Fixes https://github.com/Vector35/binaryninja-api/issues/6876
|
|
lists of values
This requires us to allocate on the rust side of the API, this is quite easy to mess up but the usage of it is limited.
|
|
This was done to fix unintended behavior using an instruction or expression index in place of the other.
Fixes https://github.com/Vector35/binaryninja-api/issues/6897
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Both of these are associated directly to a `BinaryView` and only exist as accessors onto it.
|
|
|
|
|
|
|
|
|
|
|
|
- Add unit tests
- Expose read/write functionality
- Add some much needed documentation when passing to memory map
|
|
- Don't use Result for some or none values
- Fix freeing of key value store objects
- Improve ergonomics a little bit
- Add unit tests
|
|
|
|
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.
|
|
|
|
|
|
Followup to https://github.com/Vector35/binaryninja-api/pull/5897/
This simplifies usage of the trait in user code, should just be able to `to_cstr` to get the cstr repr and then call `as_ptr`.
Co-authored-by: Michael Krasnitski <michael.krasnitski@gmail.com>
|
|
We don't need to introduce extra global state when the goal is to not release floating licenses in shutdown.
|