How to enable the always-on analysis function in settings

[romanholidaypancakes]

this function is generating excessive incremental updates ...

I don't want to click manually every time. I want it to be analyzed automatically.

[psifertex]

This is how you get infinite analysis loops that can't be stopped. I'm not sure this is something we will ever add as a setting but I will discuss it with others this week.

That said, there is an API on the function you can use so if you REALLY want to, you can write a snippet to trigger the override for all functions.

https://api.binary.ninja/binaryninja.function-module.html#binaryninja.function.Function.analysis_skipped

EDIT: You can actually get the behavior requested by setting analysis.limits.maxFunctionUpdateCount = 0 in settings. However, this will result in infinite analysis that never ends and therefore isn't a good option.

[romanholidaypancakes]

I looked at the binary and I think what you want is actually NOT to force analyze those functions. The binary is probably packed and those bytes just happen to be able to be disassembled. You should at least unpack the binary first before you continue to statically analyze it.

That said, we can still discuss whether we indeed want a way to let the user somehow force the analysis

From my experience this file is not packed, it is just obfuscated and partially virtualized

[romanholidaypancakes]

I think you need to increase your maxFunctionAnalysisTime or set it to 0 to let it take as much time as it wants.

The above picture example is the result after the analysis is completed: there are still functions that need to be forced to click (the file I tested is the file I uploaded)

[psifertex]

Did you change maxFunctionAnalysisTime to 0 as well? The last image shows that the individual functions are timing out, not that total overall analysis is timing out.

[romanholidaypancakes]

Did you change maxFunctionAnalysisTime to 0 as well? The last image shows that the individual functions are timing out, not that total overall analysis is timing out.

Setting it to 0 is useful. However, the following problems still exist:

1. When I analyze a database that I have saved before, even if I trigger re-analysis in the menu bar, the functions that needed to be clicked before still need to be clicked afterwards
2. I encountered the problem you reminded me of, and the file was still being analyzed after opening it for several hours (it seems to be stuck in an endless loop, but the analysis results are much better than before)

[psifertex]

Unfortunately the only work-around for an existing database to mass apply changes to existing functions would be to use the API, we're not considering further changes that would impact free.