debugger
debugger copied to clipboard
Support limiting the analysis on the debugger binary view to disassembly only
When debugging large binaries, or when the RIP stops in an irrelevant library, e.g., kernel32.dll, binary ninja spends considerable amount of resources analyzing the code which is not helpful for the debugging workflow. We should either offer to limit the analysis to a predefined range, or, even simpler, just limit the analysis of the debugger binary view to disassembly only. It would still be as helpful as running full analysis in more cases