| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
into dev
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
`loader.debugInfoExternal` to `analysis.debugInfo.internal` and `analysis.debugInfo.external`
|
|
|
|
Add API bindings for `BinaryView::GetDebugInfo()`, `BinaryView::ApplyDebugInfo()`, and `BinaryView::SetDebugInfo()`; Remove `analysis.experimental.parseDebugInfo`
(in favor of `loader.debugInfoInternal` and `loader.debugInfoExternal`)
|
|
This will enable us to have progress bars and cancellation of debuginfo application
|
|
|
|
|
|
|
|
|
|
|
|
debug info API"
|
|
|
|
To make use of shard functionality, we split the CoreOwnedArrayProvider
into CoreArrayProvider and CoreOwnedArrayProvider. Array makes use of
the CoreOwnedArrayProvider, which depends on CoreArrayProvider, while
the new ArrayGuard only requires CoreArrayProvider and represents
a non-owned array.
|
|
|
|
|