| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/6837
|
|
|
|
So that users of the memory map API can know if a view has activated the memory map and adjust behavior accordingly.
|
|
Fixes Vector35/binaryninja-api#6679
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now it will skip building the headless-required examples for Personal editions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
And some other misc cleanup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
`MediumLevelILInstruction` does not yet handle `MLIL_CALL_OUTPUT`,
`MLIL_CALL_PARAM`, `MLIL_CALL_PARAM_SSA`, `MLIL_CALL_OUTPUT_SSA`,
`MLIL_MEMORY_INTRINSIC_OUTPUT_SSA`, or `MLIL_MEMORY_INTRINSIC_SSA`. Map
these to a `NotYetImplemented` kind rather than panicking since a panic
takes down the entire app.
|
|
|
|
|
|
|
|
|
|
Both of these are associated directly to a `BinaryView` and only exist as accessors onto it.
|
|
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.
|
|
|
|
|
|
These are never expressed, just adds another unneeded constraint on the impl
|
|
|
|
|
