Mirrors_Framework/ghidra
1
0
Fork 0
mirror of https://github.com/NationalSecurityAgency/ghidra.git synced 2026-05-10 06:49:58 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated Frequently asked questions (markdown)

emteere
2019-06-15 10:47:00 -04:00
parent a0219990f9
commit bac6c2ea5c
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Frequently-asked-questions.md
+6
@@ -28,6 +28,12 @@ Generally, analysis time is proportional to the size of the binary. Large binari
In order to make progress on analysis for a problematic binary you can try disabling various analyzers before you perform the initial analysis via the **Analysis Options Dialog**. Using this debugging approach will not only allow your analysis to finish (minus the disabled analyzers), but it will also allow you to identify the broken analyzer(s).
### What processors are currently supported?
X86 16/32/64, ARM/AARCH64, PowerPC 32/64/VLE, MIPS 16/32/64/micro, 68xxx, Java / DEX bytecode, PA-RISC, PIC 12/16/17/18/24, Sparc 32/64, CR16C, Z80, 6502, 8051, MSP430, AVR8, AVR32, and variants of these processors.
One of the "easiest" ways to extend Ghidra is to add a new processor or extend an existing one.
### There are missing instructions or bad instructions. What can I do?
You have a couple of options: