Capstone disassembly/disassembler framework: Core (Arm, Arm64, BPF, EVM, M68K, M680X, MOS65xx, Mips, PPC, RISCV, Sparc, SystemZ, TMS320C64x, Web Assembly, X86, X86_64, XCore) + bindings.
(bloaty 依赖)
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
Issues to be solved in next versions
|
|
|
|
|
|
|
|
|
|
|
|
[Core]
|
|
|
|
|
|
|
|
- X86 cannot handle many tricks introduced by malware yet. If you find any such
|
|
|
|
instruction sequence that Capstone disassembles wrongly or fails completely,
|
|
|
|
please report. This would be the top priority of our project.
|
|
|
|
|
|
|
|
- More optimization for better performance.
|
|
|
|
|
|
|
|
- Support more operand details for Arm, Arm64, Mips & X86, especially focus on
|
|
|
|
non-standard instructions.
|
|
|
|
|
|
|
|
- At the moment the only way to get Windows binaries is cross-compiling. We have
|
|
|
|
to port the code over to Visual Studio, so those only have Windows can still
|
|
|
|
compile Capstone without needing to have Linux machine for cross-compiling.
|
|
|
|
|
|
|
|
- Reduce the binary size of libraries, so Capstone can be embeded into products.
|
|
|
|
|
|
|
|
|
|
|
|
[Bindings]
|
|
|
|
|
|
|
|
- OCaml binding are broken due to many API changes. This should be fixed ASAP.
|
|
|
|
|
|
|
|
- Python 3 support is needed.
|