| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
`loader.debugInfoExternal` to `analysis.debugInfo.internal` and `analysis.debugInfo.external`
|
|
|
|
We might need that capability again in the future, but for now default load settings are only needed on non-raw views after this
point in the API
|
|
unnecessary
|
|
Add get/set_expr_type to MLIL/HLIL Python APi
|
|
actions to load default load settings
|
|
Add API bindings for `BinaryView::GetDebugInfo()`, `BinaryView::ApplyDebugInfo()`, and `BinaryView::SetDebugInfo()`; Remove `analysis.experimental.parseDebugInfo`
(in favor of `loader.debugInfoInternal` and `loader.debugInfoExternal`)
|
|
|
|
This is [not legal](https://timsong-cpp.github.io/cppwp/n4868/vector#overview-4)
according to the C++ standard, and causes build errors in particular in C++20
mode. Fix it by defining the vector's type before using the vector.
This is a particular problem for C++20 because the compiler now generates code
for `std::vector` members earlier, due to changes to which functions are
`constexpr` in C++20. So code that was already illegal is now detected as such
by the compiler, causing errors in the vector header about the use of incomplete
types.
This was found during an internal #Cleanup at Google. No functional changes.
|
|
This will enable us to have progress bars and cancellation of debuginfo application
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/Vector35/binaryninja-api/issues/3397
|
|
|
|
|
|
|
|
|
|
|
|
variable merges
|
|
|
|
|
|
|
|
|
|
|
|
debug info API"
|
|
|
|
|
|
Due to bugs, sometimes named types will not have a correct id, leading to bugs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
