ch0ic3/cutter
1
0
Fork 0
mirror of https://github.com/rizinorg/cutter.git synced 2024-12-18 10:56:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add large bin foreground analysis issue (#2337)

Browse Source
This commit is contained in:
Surendrajat 2020-08-24 15:16:54 +05:30 committed by GitHub
parent 4fe94cd959
commit 05af1c6404
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/source/user-docs/common-issues.rst
View File

@ -17,3 +17,17 @@ Some people report that they have keyboard issues. Usually it is because
the Xorg layout is wrong. You can check it with: ``setxkbmap -query``
Most of the time using ``setxkbmap us`` solves the issue, but it might
not be enough and require a more advanced Xorg configuration.
Initial Analysis takes a long time or Cutter UI freezes
-------------------------------------------------------
Cutter and radare2 currently don't work very well with large and very large binaries.
The exact limits depend on the content of the binary, but roughly a few MB can be considered large
and may take a few minutes to analyze. More than 100MB is very large,
analysis with default settings will likely take a very long time and it might occasionally
freeze the UI during usage.
If the analysis takes longer than 5-15 minutes it is recommended to retry it with different
analysis options. In the "Load Options" dialog, move the analysis slider to the right in order to reach
the "Advanced Analysis" view. This view will help you learn more about the options that can
be used to more selectively analyze only the relevant parts of code.