xusheng
xusheng
A fix will be coming soon for it
@mr-tz please add the "binary-ninja" tag on this issue and also https://github.com/mandiant/capa/issues/2489, https://github.com/mandiant/capa/issues/2499, https://github.com/mandiant/capa/issues/2496
We are unlikely to create a way to force analysis to be done when it exceeds the thresholds, at least headlessly. That will be way too easy to lead to...
This is actually caused by https://github.com/Vector35/binaryninja-api/issues/6020
> Thanks for looking into all these issues, @xusheng6! I love how capa helps to improve other analysis tools. > > I've added the labels and will keep an eye...
Status update on this: 1. The crash happens due to an oversight that the IL of a function can be unavailable in an unexpected way. The crash itself is fixed...
> How high does memory usage grow if we cache *all* of the IL for a program? > > > > Within capa (specifically, the capa Binja backend/integration), we could...
@copilot also update the code to handle the case where we resume the target, it executes and then exits. Right now the debugger would not be aware of the target...
@copilot There seems to be a synchronization issue when waiting for the response for `info proc mappings`. The relevant logs are attached. Identify the root cause and propose a fix...
@copilot Your fix does not work. I think the issue could actually be that while the response for "info proc mappings" has not been fully received, another memory request is...